| 2.1 |
Approval of the agenda |
|
| R2-2307000 |
Agenda for RAN2#123 |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2307001 |
RAN2#122 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2307002 |
RAN2 Handbook |
MCC |
| R2-2308274 |
|
MCC |
| R2-2308741 |
Guidance for IAB/NCR CRs on checking the box of ME |
Huawei, HiSilicon |
| R2-2309222 |
Guidance for IAB/NCR CRs on checking the box of ME |
Huawei, HiSilicon, Samsung, Ericsson, Nokia, ZTE, Qualcomm Incorporated |
| R2-2309272 |
Positioning Information Transfer |
R3 (Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CMCC) |
| R2-2309273 |
Correction to missing NRPPa procedures |
R3 (Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CMCC) |
| R2-2309274 |
Correction on R17 MO SDT termination |
R3 (ZTE, China Telecom, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, CATT, Ericsson, Xiaomi, LG Electronics, Samsung) |
| R2-2309275 |
Correction on mobility restriction list for MR-DC with 5GC |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange) |
| R2-2309276 |
Correction on mobility restriction list for MR-DC with 5GC |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange) |
| 3 |
Incoming liaisons |
|
| R2-2307071 |
Reply LS on Research highlighting potential 5G and 4G Bidding Down Attacks (S3-233321; contact: Qualcomm) |
SA3 |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2307514 |
MAC correction on drx-InactivityTimer for eMTC and NB-IOT UE |
Xiaomi |
| R2-2307631 |
Correction to enable flightPathInfoAvailable indication when connected to 5GC |
Qualcomm Incorporated |
| R2-2308760 |
Correction on alternative cell reselection priority |
Google Inc. |
| R2-2308762 |
Correction on alternative cell reselection priority |
Google Inc. |
| 4.2 |
NB-IoT and eMTC support for NTN Rel-17 |
|
| R2-2307188 |
Clarify the reference point for timing info in SIB16(-NB) and DLInformationTransfer in IoT NTN |
MediaTek Inc., Qualcomm Inc, Apple, Ericsson, Huawei |
| R2-2307324 |
Corrections on the HARQ RTT timer for IoT NTN |
MediaTek |
| R2-2307325 |
Correct TrackingAreaList for selected PLMN for NB-IoT |
MediaTek |
| R2-2307499 |
Discussion on UTC reference point in IoT NTN |
Huawei, HiSilicon |
| R2-2308227 |
Reference point for UTC timing in SIB16(-NB) |
Nokia, Nokia Shanghai Bell |
| R2-2308522 |
Miscellaneous RRC corrections for IoT NTN |
ZTE Corporation, Sanechips |
| R2-2308538 |
Correction to GNSS acquisition description for IoT NTN |
Ericsson |
| R2-2308893 |
RRC Correction on including GNSS validity duration and dedicated SIB31 |
Samsung |
| R2-2308983 |
Clarify the reference point for timing info in SIB16(-NB) and DLInformationTransfer in IoT NTN |
MediaTek Inc., Qualcomm Inc, Apple, Ericsson, Huawei |
| R2-2308984 |
Miscellaneous RRC corrections for IoT NTN |
ZTE Corporation, Sanechips |
| R2-2308985 |
RRC Correction on including GNSS validity duration and dedicated SIB31 |
Samsung |
| R2-2308986 |
Corrections on the HARQ RTT timer for IoT NTN |
MediaTek |
| R2-2308992 |
Clarify the reference point for timing info in SIB16(-NB) and DLInformationTransfer in IoT NTN |
MediaTek Inc., Qualcomm Inc, Apple, Ericsson, Huawei |
| R2-2308994 |
Miscellaneous RRC corrections for IoT NTN |
ZTE Corporation, Sanechips, Qualcomm Incorporated, MediaTek Inc. |
| R2-2308995 |
Miscellaneous MAC corrections for IoT NTN |
MediaTek Inc., ZTE Corporation, Sanechips, Qualcomm Incorporated |
| R2-2309263 |
Report of [AT123][105][IoT NTN] RRC CR 4952 (Samsung) |
Samsung |
| R2-2309292 |
Clarify the reference point for timing info in SIB16(-NB) and DLInformationTransfer in IoT NTN |
MediaTek Inc., Qualcomm Inc, Apple, Ericsson, Huawei |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2307049 |
Reply LS on intraBandENDC-Support (R4-2310501; contact: Huawei, Xiaomi) |
RAN4 |
| R2-2307050 |
LS on frequencyInfo for NR SL RSRP measurements (R5-233768; contact: Huawei) |
RAN5 |
| R2-2308742 |
Stage2 correction on UE Identities |
Huawei, Nokia (Rapporteur), HiSilicon |
| R2-2308743 |
Stage2 correction on UE Identities |
Huawei, Nokia (Rapporteur), HiSilicon |
| 5.1.2.1 |
MAC |
|
| R2-2308660 |
Clarification on the trigger of MAC events |
Huawei, HiSilicon |
| R2-2308661 |
Clarification on the trigger of MAC events (Rel-16) |
Huawei, HiSilicon |
| R2-2308662 |
Clarification on the trigger of MAC events (Rel-16) |
Huawei, HiSilicon |
| R2-2308669 |
Clarification on the trigger of MAC events (Rel-17) |
Huawei, HiSilicon |
| 5.1.3.1 |
NR RRC |
|
| R2-2307326 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307327 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307328 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307331 |
Clarification to release and add of BWP-UplinkDedicated |
Nokia, Nokia Shanghai Bell |
| R2-2307332 |
Clarification to release and add of BWP-UplinkDedicated |
Nokia, Nokia Shanghai Bell |
| R2-2307333 |
Clarification to release and add of BWP-UplinkDedicated |
Nokia, Nokia Shanghai Bell |
| R2-2307337 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307338 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307339 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2307922 |
Correction on ReportInterval |
Samsung |
| R2-2307923 |
Correction on ReportInterval |
Samsung |
| R2-2307924 |
Correction on ReportInterval |
Samsung |
| R2-2307937 |
Correction to RRC on multi-PDSCH |
Ericsson |
| R2-2308055 |
Discussion on CSI-RS coordination in NR-DC |
ZTE Corporation, Sanechips |
| R2-2308056 |
Introducing CSI-RS coordination in NR-DC |
ZTE Corporation, Sanechips |
| R2-2308057 |
Introducing CSI-RS coordination in NR-DC |
ZTE Corporation, Sanechips |
| R2-2308177 |
On the Absence of the DMRS Configuration for PUSCH |
Google Inc. |
| R2-2308190 |
Corrections to ensure the presence of the DMRS configuration |
Google Inc. |
| R2-2308191 |
Corrections to the TimeDomainResourceAllocationList field description |
Google Inc. |
| R2-2308248 |
Miscellaneous non-controversial corrections Set XIX |
Ericsson |
| R2-2308249 |
Miscellaneous non-controversial corrections Set XIX |
Ericsson |
| R2-2308430 |
Misalignment behavior in changing the security algorithms |
Ericsson |
| R2-2308536 |
Correction on the conditional presence for primarypath |
Huawei, HiSilicon |
| R2-2308537 |
Correction on the conditional presence for primarypath |
Huawei, HiSilicon |
| R2-2308645 |
Correction on CHO for R16 |
Huawei, HiSilicon |
| R2-2308646 |
Correction on CHO for R17 |
Huawei, HiSilicon |
| R2-2308678 |
Correction on the field description of DormantBWP-Config |
Samsung |
| R2-2308680 |
Correction on the field description of DormantBWP-Config |
Samsung |
| R2-2308751 |
Periodical measurement reporting with reportAmount set to one |
Nokia, Nokia Shanghai Bell |
| R2-2308754 |
Periodical measurement reporting with reportAmount set to one |
Nokia, Nokia Shanghai Bell |
| R2-2308757 |
Periodical measurement reporting with reportAmount set to one |
Nokia, Nokia Shanghai Bell |
| R2-2308792 |
Clarification on sCellState upon SCell modification |
Xiaomi |
| R2-2308793 |
Clarification on sCellState upon SCell modification |
Xiaomi |
| R2-2309011 |
CSI-RS resource coordination |
Nokia, Nokia Shanghai Bell |
| R2-2309012 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2309192 |
Correction on primaryPath for fast MCG link recovery |
Huawei, HiSilicon |
| R2-2309193 |
Correction on primaryPath for fast MCG link recovery |
Huawei, HiSilicon |
| R2-2309236 |
Correction on CHO for R16 |
Huawei, HiSilicon, Ericsson |
| R2-2309237 |
Correction on CHO for R17 |
Huawei, HiSilicon, Ericsson |
| R2-2309289 |
CSI-RS resource coordination in NR-DC |
Nokia, Nokia Shanghai Bell |
| 5.1.3.2 |
UE capabilities |
|
| R2-2307043 |
LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 (R4-2310170; contact: Apple) |
RAN4 |
| R2-2307545 |
Consideration on the interBandMRDC-WithOverlapDL-Bands-r16 |
ZTE Corporation, Sanechips |
| R2-2307699 |
Correction on update for the interBandMRDC-WithOverlapDL-Bands-r16 |
Samsung |
| R2-2307700 |
Correction on update for the interBandMRDC-WithOverlapDL-Bands-r16 |
Samsung |
| R2-2307860 |
Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Ericsson, Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2307861 |
Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Ericsson, Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2307862 |
Update on UE capability interBandMRDC-WithOverlapDL-Bands-r16 |
Apple, Ericsson, Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2307880 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple |
| R2-2307881 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple |
| R2-2307882 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple |
| R2-2308510 |
Update to interBandMRDC-WithOverlapDL-Bands-r16 |
Nokia, Nokia Shanghai Bell |
| R2-2308511 |
Update to interBandMRDC-WithOverlapDL-Bands-r16 |
Nokia, Nokia Shanghai Bell |
| R2-2308512 |
Discussion on interBandMRDC-WithOverlapDL-Bands-r16 |
Nokia, Nokia Shanghai Bell |
| R2-2308599 |
Clarification on UE Gap Capabilities for EN-DC Band Combination |
Samsung |
| R2-2308601 |
Clarification on UE Gap Capabilities for EN-DC Band Combination |
Samsung |
| R2-2308602 |
Clarification on UE Gap Capabilities for EN-DC Band Combination |
Samsung |
| R2-2308907 |
(Draft) Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16” in 38.306 |
ZTE Corporation, Sanechips |
| R2-2309165 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| R2-2309166 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| R2-2309167 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| R2-2309212 |
[DRAFT] Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16 |
Apple |
| R2-2309218 |
Reply LS on update for “interBandMRDC-WithOverlapDL-Bands-r16 in 38.306 |
RAN2 |
| R2-2309300 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| R2-2309301 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| R2-2309302 |
Correction on the interpretation of the UE capability field simultaneousRxTxInterBandENDC |
Apple Inc. |
| 5.1.3.3 |
Other |
|
| R2-2307329 |
Correction to NS-value utilization |
Nokia, Nokia Shanghai Bell |
| R2-2307330 |
Correction to NS-value utilization |
Nokia, Nokia Shanghai Bell |
| R2-2309009 |
Correction to NS-value utilization |
Nokia, Nokia Shanghai Bell |
| R2-2309010 |
Correction to NS-value utilization |
Nokia, Nokia Shanghai Bell |
| 5.2 |
NR V2X |
|
| R2-2307096 |
Correction on PUCCH resource field description and SSB transmission initiation |
OPPO |
| R2-2307097 |
Correction on PUCCH resource field description and SSB transmission initiation |
OPPO |
| R2-2307503 |
Correction on NR Sidelink MAC |
Philips International B.V. |
| R2-2307562 |
Potential issue caused by using destination index |
Huawei, HiSilicon, vivo, Ericsson |
| R2-2307563 |
Correction on destination index for SL measurement configuration |
Huawei, HiSilicon, vivo, Ericsson |
| R2-2307564 |
Correction on destination index for SL measurement configuration |
Huawei, HiSilicon, vivo, Ericsson |
| R2-2307565 |
Correction on destination index for SL DRX configuration |
Huawei, HiSilicon, vivo, Ericsson |
| R2-2307566 |
Draft reply LS on frequencyInfo for NR SL RSRP measurements |
Huawei, HiSilicon |
| R2-2307567 |
Correction on carrier frequency for SL-RSRP measurement |
Huawei, HiSilicon |
| R2-2307568 |
Correction on carrier frequency for SL-RSRP measurement |
Huawei, HiSilicon |
| R2-2307569 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R2-2307570 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R2-2307753 |
Correction on NR Sidelink RRC |
Philips International B.V. |
| R2-2307754 |
Correction on NR Sidelink RRC |
Philips International B.V. |
| R2-2308105 |
Correction on sidelink measurement |
ZTE Corporation, Sanechips |
| R2-2308106 |
Correction on sidelink measurement |
ZTE Corporation, Sanechips |
| R2-2308107 |
Discussion on LS from RAN5 |
ZTE Corporation, Sanechips |
| R2-2308431 |
Miscellaneous stage 2 corrections for sidelink |
Ericsson |
| R2-2308432 |
Miscellaneous stage 2 corrections for sidelink |
Ericsson |
| R2-2308561 |
Summary on NR V2X RRC corrections |
Huawei, HiSilicon |
| R2-2308709 |
Correction on SL transmissions during measurement gap |
ASUSTeK |
| R2-2308710 |
Correction on SL transmissions during measurement gap |
ASUSTeK |
| R2-2308933 |
Correction on carrier frequency for SL-RSRP measurement |
Huawei, HiSilicon |
| R2-2308934 |
Correction on carrier frequency for SL-RSRP measurement |
Huawei, HiSilicon |
| R2-2309121 |
Summary of [501][V2X/SL] SL 38.300 corrections (Ericsson) |
Ericsson |
| R2-2309122 |
Miscellaneous stage 2 corrections for sidelink |
Ericsson |
| R2-2309123 |
Miscellaneous stage 2 corrections for sidelink |
Ericsson |
| R2-2309124 |
Summary on [AT123][502][V2X/SL] SL 38.331 corrections (Huawei) |
Huawei, HiSilicon |
| R2-2309125 |
Miscellaneous NR V2X RRC corrections |
Huawei, HiSilicon, vivo, Ericsson, Philips International B.V., ZTE Corporation, Sanechips |
| R2-2309126 |
Miscellaneous NR V2X RRC corrections |
Huawei, HiSilicon, vivo, Ericsson, Philips International B.V., ZTE Corporation, Sanechips |
| R2-2309127 |
Summary on [AT123][503][V2X/SL] SL 38.321 corrections (ASUSTeK) |
ASUSTeK |
| R2-2309128 |
Correction on NR Sidelink MAC |
Philips International B.V. |
| R2-2309130 |
On frequencyInfo for NR SL RSRP measurements |
RAN2 |
| R2-2309138 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R2-2309139 |
Miscellaneous corrections on TR 37.985 |
Huawei, HiSilicon |
| R2-2309153 |
On miscellaneous corrections on TR 37.985 |
RAN2 |
| R2-2309159 |
On frequencyInfo for NR SL RSRP measurements |
RAN2 |
| R2-2309209 |
LS on SL transmission and reception regarding measurement gaps |
ASUSTeK |
| R2-2309291 |
Correction on PUCCH resource field description and SSB transmission initiation |
OPPO |
| R2-2309295 |
Correction on NR Sidelink MAC |
Philips International B.V. |
| 5.3.1 |
General and Stage 2 corrections |
|
| R2-2307357 |
Correction to 38.305 on E-CID |
Huawei, HiSilicon |
| R2-2307358 |
Correction to 38.305 on E-CID |
Huawei, HiSilicon |
| R2-2308268 |
LS on SSR orbit and clock correction reference for BDS in 3GPP LPP (contact: Ericsson) |
RTCM SC 104 |
| R2-2308476 |
GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM |
Ericsson |
| R2-2308477 |
GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM |
Ericsson |
| R2-2309102 |
GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM |
Ericsson |
| R2-2309103 |
GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM |
Ericsson |
| R2-2309293 |
GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM |
Ericsson |
| 5.3.3 |
LPP corrections |
|
| R2-2308474 |
Correcting GNSS Ionospheric and Troposperic Delay Correction quality representation |
Ericsson |
| R2-2308475 |
Correcting GNSS Ionospheric and Troposperic Delay Correction quality representation |
Ericsson |
| R2-2308688 |
Addition of missing field description for nr-DL-PRS-ResourceID/nr-DL-PRS-ResourceSetID |
Samsung |
| R2-2308689 |
Addition of missing field description for nr-DL-PRS-ResourceID/nr-DL-PRS-ResourceSetID |
Samsung |
| 5.4 |
SON MDT support for NR |
|
| R2-2309258 |
Correction on location configuration for WLAN, BT and sensor for SON and MDT features |
Huawei, HiSilicon |
| R2-2309259 |
Correction on location configuration for WLAN, BT and sensor for SON and MDT features |
Huawei, HiSilicon |
| R2-2309260 |
Correction on location configuration for WLAN and BT for SON and MDT features |
Huawei, HiSilicon |
| R2-2309261 |
Correction on location configuration for WLAN and BT for SON and MDT features |
Huawei, HiSilicon |
| R2-2309262 |
Correction on location configuration for WLAN and BT for SON and MDT features |
Huawei, HiSilicon |
| R2-2309298 |
Correction on location configuration for WLAN and BT for SON and MDT features |
Huawei, HiSilicon |
| 5.4.3 |
RRC corrections |
|
| R2-2307783 |
Add offsetToCarrier parameter in RA Report |
CATT, CMCC |
| R2-2307784 |
Add offsetToCarrier parameter in RA Report |
CATT, CMCC |
| R2-2308417 |
Clarification to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2308418 |
Clarification to the setting of locationInfo in MeasResultSCG-Failure |
Ericsson |
| R2-2308419 |
PLMN check for the reconnectCellID in the RLF report |
Ericsson |
| R2-2308420 |
PLMN check for the reconnectCellID in the RLF report |
Ericsson |
| R2-2308556 |
Correction on UE behavior for RLF report upon detection of T312 expiry |
Qualcomm Incorporated |
| R2-2308642 |
Discussion on location configuration for WLAN, BT and sensor for SON and MDT features |
Huawei, HiSilicon |
| R2-2308671 |
Correction on storage of RLF information upon T312 expiry in PCell_Opt 1 |
Samsung |
| R2-2308674 |
Correction on storage of RLF information upon T312 expiry in PCell_Opt 2 |
Samsung |
| R2-2309025 |
Clarification on the PLMN check for the reconnectCellID in the RLF report |
Ericsson |
| R2-2309026 |
Clarification on the PLMN check for the reconnectCellID in the RLF report |
Ericsson |
| R2-2309299 |
Clarification on the PLMN check for the reconnectCellID in the RLF report |
Ericsson |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2307006 |
Reply LS to RAN2 on unified TCI-state and fast SCell activation (R1-2306197; contact: ZTE) |
RAN1 |
| R2-2307026 |
Reply LS on Mapping of F1-C IP addresses in the IAB inter-CU topology adaptation and backhaul RLF recovery procedures (R3-232166; contact: ZTE) |
RAN3 |
| R2-2307028 |
Reply LS on the use of PEI during an Emergency PDU Session (R3-233313; contact: Nokia) |
RAN3 |
| R2-2307033 |
LS on applicability of pre-configured measurement gaps for RedCap UE (R3-233478; contact: Qualcomm) |
RAN3 |
| R2-2307046 |
LS on Rel-17 DC location signaling enhancement (R4-2310438; contact: Apple) |
RAN4 |
| R2-2307061 |
Reply LS on the use of PEI during an emergency PDU session (S2-2307974; contact: Ericsson)) |
SA2 |
| R2-2307062 |
Reply to LS on addressing packet loss during multicast MBS delivery (S2-2307982; contact: Ericsson) |
SA2 |
| R2-2307513 |
Correction for SDT |
Xiaomi |
| R2-2307617 |
Miscellaneous stage 2 corrections on NR QoE |
Lenovo |
| R2-2307633 |
Discussion on and draft reply to SA2 LS on addressing packet loss during multicast MBS delivery |
Qualcomm Incorporated |
| R2-2307646 |
Draft Reply LS on applicability of pre-configured measurement gaps for RedCap UE |
Qualcomm Incorporated |
| R2-2308058 |
Correction on gap requirement for inter-RAT LTE measurement |
ZTE Corporation, Sanechips |
| R2-2308799 |
Clarifications for MBS service continuity |
Samsung |
| R2-2308919 |
Correction on SDT Triggering |
vivo, Nokia |
| R2-2308923 |
RedCap specific SDT configuration |
Nokia, Nokia Shanghai Bell |
| R2-2308942 |
Correction on gap requirement for inter-RAT LTE measurement |
ZTE Corporation, Sanechips, Nokia (Rapporteur) |
| R2-2308958 |
Correction for SDT |
Xiaomi |
| R2-2309190 |
RedCap specific SDT configuration |
Nokia, Nokia Shanghai Bell |
| R2-2309191 |
Reply LS on applicability of pre-configured measurement gaps for RedCap UE |
RAN2 |
| R2-2309195 |
Correction for SDT |
Xiaomi |
| R2-2309216 |
Correction on SDT |
Xiaomi |
| 6.1.2 |
User Plane corrections |
|
| R2-2307958 |
Correction on the use of the term ID in IAB MAC CEs |
Samsung, Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2307983 |
Clarification on use of SRI in IAB MAC CEs |
Samsung |
| R2-2308433 |
Correction on number of restricted beams for eIAB |
Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R2-2308499 |
Correction to PDCCH monitoring |
Google Inc. |
| R2-2308711 |
DRX Command MAC CE for MBS |
ASUSTeK |
| R2-2308906 |
Correction on TCI-state for RedCap UE |
ZTE Corporation, Sanechips |
| R2-2308922 |
Correction on SDT Triggering Conditions |
vivo |
| R2-2308924 |
Correction on HARQ buffer flush at SCG deactivation |
Nokia, Apple, Mediatek, Qualcomm, Nokia Shanghai Bell |
| R2-2308925 |
Correction on BFI_COUNTER at SCG activation |
Nokia, Nokia Shanghai Bell |
| R2-2309196 |
Correction on number of restricted beams for eIAB |
Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R2-2309210 |
Correction on SDT Triggering Conditions |
vivo |
| R2-2309217 |
DRX Command MAC CE for MBS |
ASUSTeK |
| 6.1.3.1 |
NR RRC |
|
| R2-2307205 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2307206 |
Correction on Type1 HARQ-ACK codebook generation |
Qualcomm Incorporated |
| R2-2307266 |
Corrections to TS 38.331 on MBS Broadcast |
CATT, CBN |
| R2-2307267 |
Correction to TS 38.331 on MBS Multicast |
CATT, CBN |
| R2-2307377 |
Discussion on the uniqueness of search space IDs among initial BWPs |
Qualcomm Incorporated |
| R2-2307378 |
Discussion on the autonomous BWP switching beyond UE's configured channel bandwidth |
Qualcomm Incorporated |
| R2-2307438 |
Change Request on UE Capability of Enhanced Type 3 HARQ-ACK Codebook supporting 32 HARQ processes for PUCCH group |
vivo |
| R2-2307439 |
Correction on Configuration of Enhanced Type 3 HARQ-ACK Codebook for PUCCH group |
vivo |
| R2-2307440 |
Discussion on Configuration of Enhanced Type 3 HARQ-ACK Codebook for PUCCH group |
vivo |
| R2-2307467 |
Correction on PUCCH Repetition for PUCCH Format 2 |
vivo |
| R2-2307468 |
Discussion on CSI-RS resource coordination in NR-DC |
vivo |
| R2-2307490 |
Miscellaneous RRC corrections for MBS |
Huawei, CBN, HiSilicon |
| R2-2307491 |
Discussion on the remaining RRC issues for MBS |
Huawei, CBN, HiSilicon |
| R2-2307515 |
Correction on RLM/BFD relaxation state reporting |
Nokia, Nokia Shanghai Bell |
| R2-2307632 |
Correction to repetitionNumber-r16 in PDSCH-TimeDomainResourceAllocation-r16 |
Qualcomm Incorporated |
| R2-2307674 |
Corrections on the unified TCI-state configuration for 38.331 |
Xiaomi, ZTE Corporation |
| R2-2307677 |
Clarification on the broadcast CFR configuration |
Xiaomi |
| R2-2307701 |
Clarification on the condition of subband reporting |
Samsung |
| R2-2307702 |
Correction of the RS configuration for group based beam reporting |
Samsung |
| R2-2307703 |
RRC restriction on muti-TRP schemes |
Samsung |
| R2-2307764 |
SA2 LS discussion on packet loss |
Nokia, Nokia Shanghai Bell |
| R2-2307912 |
Correction to RRC for 71 GHz on multi-PUSCH |
Ericsson, LG Electronics Inc., ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, Huawei, HiSilicon |
| R2-2307916 |
Further correction to RRC for 71 GHz on multi-PUSCH |
Ericsson, Xiaomi, ASUSTeK, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics Inc |
| R2-2307921 |
Correction on buffer levels and storing QoE reports |
Samsung |
| R2-2307925 |
Correction on PDCP-Config |
Samsung |
| R2-2307933 |
Discussion on PUCCH Repetition for PUCCH Format 2 |
vivo |
| R2-2307935 |
Further discussion on k2 for multi-PUSCH |
Ericsson |
| R2-2307936 |
Removal of out of dated editor’s notes for 71 GHz |
Ericsson, Huawei, HiSilicon |
| R2-2307938 |
Correction to RRC for 71 GHz on multi-PDSCH |
Ericsson |
| R2-2308059 |
Discussion on pre-configured gap for RedCap UE |
ZTE Corporation, Sanechips |
| R2-2308062 |
Clarification on the BFD Resource for mTRP |
ZTE Corporation, Sanechips |
| R2-2308063 |
Clarification on CE-only BWP |
ZTE Corporation, Sanechips |
| R2-2308064 |
Consideration on DC location reporting |
ZTE Corporation, Sanechips |
| R2-2308108 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2308111 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2308112 |
Corrections on the search space for RedCap |
Huawei, HiSilicon |
| R2-2308113 |
Clarification on the searchSpaceId field description |
Huawei, HiSilicon |
| R2-2308114 |
Corrections on relaxedMeasurement and initialUplinkBWP-RedCap |
Huawei, China Southern Power Grid, HiSilicon |
| R2-2308115 |
Correction on the HD-FDD indication and per band capability for RedCap |
Huawei, HiSilicon |
| R2-2308192 |
Corrections on RedCap CFR for MBS broadcast |
Xiaomi,Huawei, HiSilicon, Ericsson |
| R2-2308250 |
Miscellaneous non-controversial corrections Set XIX |
Ericsson |
| R2-2308347 |
Discussion about SA2 LS on packet loss during multicast MBS delivery (with draft LS) |
ZTE, Sanechips |
| R2-2308365 |
Correction on description of cell reselection priority in TS 38.331 |
CATT |
| R2-2308366 |
Correction on description of FeaturePriorities in TS 38.331 |
CATT |
| R2-2308647 |
Miscellaneous corrections for power saving features |
Huawei, HiSilicon |
| R2-2308691 |
Correction on procedure text for gapToAddModList configuration. |
Samsung |
| R2-2308712 |
Correction on 2-step RACH configuration for feature combination |
ASUSTeK |
| R2-2308713 |
Correction on pair of CSI |
ASUSTeK |
| R2-2308763 |
Correction on dedicated system information delivery for MBS |
MediaTek Inc. |
| R2-2308803 |
Clarification on condition for a UE to apply ran-PagingCycle, when eDRX-AllowedInactive is absent |
Ericsson |
| R2-2308931 |
Correction for group based beam reporting configuration |
Huawei, HiSilicon |
| R2-2308951 |
Corrections to TS 38.331 on MBS |
CATT, CBN |
| R2-2309161 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309162 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309163 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309164 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309197 |
RRC restriction on muti-TRP schemes |
Samsung |
| R2-2309198 |
Correction to RRC for 71 GHz on multi-PDSCH |
Ericsson |
| R2-2309203 |
Corrections on the search space for RedCap |
Huawei, HiSilicon |
| R2-2309213 |
Correction on Configuration of Enhanced Type 3 HARQ-ACK Codebook for PUCCH group |
vivo |
| R2-2309215 |
Summary of Offline #020 Autonomous BWP switching beyond UE’s configured channel bandwidth |
Qualcomm Incorporated |
| R2-2309220 |
Correction on PUCCH repetition for PUCCH Format 2 |
vivo, Nokia, Nokia Shanghai Bell |
| R2-2309221 |
Corrections to TS 38.331 on MBS |
CATT, CBN |
| R2-2309223 |
Summary of Offline 019 Uniqueness of search space IDs and coreset IDs among initial BWPs |
Qualcomm Incorporated |
| R2-2309235 |
Miscellaneous RRC corrections for MBS |
Huawei, CBN, HiSilicon |
| R2-2309239 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309240 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309241 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309242 |
Redirection with MPS correction for resume cause |
Peraton Labs, CISA ECD, AT&T, T-Mobile USA, Verizon |
| R2-2309243 |
[DRAFT] Reply to LS on addressing packet loss during multicast MBS delivery |
Qualcomm Incorporated |
| R2-2309244 |
Miscellaneous RRC corrections for MBS |
Huawei, CBN, HiSilicon, CATT, Qualcomm, Samsung, MediaTek |
| R2-2309245 |
Reply to LS on addressing packet loss during multicast MBS delivery |
RAN2 |
| R2-2309277 |
Miscellaneous non-controversial corrections Set XIX |
Ericsson |
| R2-2309296 |
Correction on Configuration of Enhanced Type 3 HARQ-ACK Codebook for PUCCH group |
vivo |
| R2-2309297 |
Correction on PUCCH repetition for PUCCH Format 2 |
vivo, Nokia, Nokia Shanghai Bell |
| 6.1.3.2 |
UE capabilities |
|
| R2-2307094 |
Discussion on ue-PowerClassPerBandPerBC-r17 |
OPPO |
| R2-2307202 |
Backward compatibility analysis on new UE capability signalling of maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated, Apple, Ericsson |
| R2-2307203 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated, Apple, Ericsson |
| R2-2307204 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA |
Qualcomm Incorporated, Apple, Ericsson |
| R2-2307874 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA |
Apple Inc , Qualcomm Incorporated, Ericsson |
| R2-2307875 |
Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA |
Apple Inc , Qualcomm Incorporated, Ericsson |
| R2-2307876 |
Building on agg BW signaling for FR2 R2-R12 BW classes |
Apple, Qualcomm, Ericsson |
| R2-2308060 |
Clarification on multipleCORESET for RedCap UE |
ZTE Corporation, Sanechips |
| R2-2308061 |
Correction on multipleCORESET for RedCap UE |
ZTE Corporation, Sanechips |
| R2-2308491 |
Filter of SRS carrier switching capabilities |
Ericsson |
| R2-2308509 |
Clarification on ue-PowerClassPerBandPerBC-r17 |
Nokia, Nokia Shanghai Bell |
| R2-2308648 |
Discussion on newly introduced FR2 CA BW Classes |
Huawei, HiSilicon |
| R2-2308826 |
Correction of the capability independentGapConfig-maxCC |
Qualcomm Incorporated, Ericsson |
| R2-2308827 |
Correction of the capability independentGapConfig-maxCC |
Qualcomm Incorporated, Ericsson |
| R2-2308849 |
Further considerations on new signaling of maximum aggregated bandwidth |
MediaTek Inc. |
| R2-2308851 |
Introduction of aggregated bandwidth capability signaling |
MediaTek Inc. |
| R2-2308852 |
Introduction of aggregated bandwidth capability signaling |
MediaTek Inc. |
| R2-2308854 |
Miscellaneous corrections on UE capabilities |
Huawei, HiSilicon |
| R2-2308855 |
Relay LS on intraBandENDC-Support |
RAN2 |
| R2-2308856 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc. , OPPO |
| R2-2308857 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc. , OPPO |
| R2-2308858 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc., OPPO |
| R2-2308859 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc, OPPO |
| R2-2308860 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc, OPPO |
| R2-2308861 |
Introduction of intra-band EN-DC contiguous capability for UL |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Intel Corporation, ZTE Corporation, Sanechips, MediaTek inc, OPPO |
| R2-2308862 |
Discussion on the maximum aggregated bandwidth |
Huawei, HiSilicon |
| R2-2308909 |
Introduction of FR2 FBG2 CA BW classes |
ZTE Corporation, Sanechips |
| R2-2308980 |
Miscellaneous corrections on UE capabilities |
Huawei, HiSilicon |
| R2-2309208 |
Summary of offline discussion [AT123][008] Aggregated BW (Qualcomm) |
Qualcomm Incorporated |
| R2-2309214 |
Draft Reply LS on newly introduced FR2 CA BW Classes |
Huawei, HiSilicon |
| R2-2309219 |
Reply LS on newly introduced FR2 CA BW Classes |
RAN2 |
| 6.1.3.3 |
Other |
|
| R2-2308251 |
NSAG validity when TAI list is omitted |
Ericsson |
| R2-2308252 |
NSAG validity when TAI list is omitted |
Ericsson |
| R2-2309206 |
NSAG validity when TAI list is omitted |
Ericsson |
| R2-2309303 |
NSAG validity when TAI list is omitted |
Ericsson |
| 6.2.1 |
Control plane and Stage-2 corrections |
|
| R2-2307194 |
38.331_CR_Corrections to processing of paging information received via Relay UE |
Samsung Electronics Co., Ltd |
| R2-2307239 |
Correction of RemoteUEInformationSidelink transmission condition |
OPPO |
| R2-2307727 |
Conditions for RRC connection establishment and resume for NR sidelink discovery |
Samsung, Huawei, HiSilicon |
| R2-2307755 |
Correction on NR Sidelink Relay RRC |
Philips International B.V. |
| R2-2307852 |
Corrections on SRAP related configurations for SL relay |
Apple |
| R2-2307853 |
Corrections on the reporting of L2 ID for L2 U2N relay operation |
Apple |
| R2-2307955 |
Correction on CHO and Path Switching of Remote UE |
NEC Corporation |
| R2-2308210 |
Miscellaneous corrections for SL relay |
Huawei, HiSilicon |
| R2-2308271 |
Corrections to TS 38.331 on SL relay (re)selection |
ZTE, CAICT, Sanechips |
| R2-2308272 |
Corrections to TS38.300 on SL relay (re)selection |
ZTE, CAICT, Sanechips |
| R2-2308275 |
Correction to 38.331 on U2N relay (re)selection |
vivo |
| R2-2308550 |
Miscellaneous Corrections for SL Relays |
Ericsson España S.A. |
| R2-2308553 |
Miscellaneous Correction for SL Relays |
Ericsson |
| R2-2308714 |
Corrections on U2N Relay |
ASUSTeK |
| R2-2308953 |
[Pre123][401][Relay] Summary of AI 6.2.1 on Rel-17 relay control plane (Huawei) |
Huawei |
| R2-2309109 |
RRC corrections for SL relay |
Huawei, HiSilicon, Apple, ASUSTeK, Ericsson, Philips International B.V., Samsung, vivo |
| R2-2309252 |
RRC corrections for SL relay |
Huawei, HiSilicon, Apple, ASUSTeK, Ericsson, Philips International B.V., Samsung, vivo |
| 6.2.2 |
User plane corrections |
|
| R2-2307238 |
Correction of IE name sl-SRAP-ConfigRemote |
OPPO |
| R2-2307756 |
Correction on SRAP for sidelink relay |
Philips International B.V. |
| R2-2308211 |
Clarification on the BEARER ID in SRAP data PDU |
Huawei, HiSilicon |
| R2-2309110 |
Clarification on the BEARER ID in SRAP data PDU |
Huawei, HiSilicon |
| R2-2309111 |
Correction on SRAP for sidelink relay |
Philips International B.V. |
| R2-2309290 |
Correction on SRAP for sidelink relay |
Philips International B.V., Nokia, Samsung, Apple |
| 6.3 |
NR Non-Terrestrial Networks (NTN) |
|
| R2-2307113 |
Correction on the Capability of TA Reporting |
vivo |
| R2-2307498 |
Triggering of TA Report during handover |
Huawei, HiSilicon |
| R2-2308253 |
Clarification of UE configuration in TN and NTN |
Ericsson |
| R2-2308520 |
Correction on RRC Release for NR NTN |
Samsung |
| R2-2308987 |
Report of [AT123][107][NR NTN] RRC CR 4239 (Samsung) |
Samsung |
| 6.4.1 |
Stage 3 corrections |
|
| R2-2307359 |
Correction to Multi-RTT |
Huawei, HiSilicon |
| R2-2307360 |
Correction to UE capability for batch reporitng |
Huawei, HiSilicon |
| R2-2307504 |
Missing error cause code for DL PRS Measurements |
Fraunhofer IIS, Ericsson |
| R2-2308478 |
Missing finer periodicities than 1s |
Ericsson |
| R2-2308479 |
Missing LPP support for sub 1s location information reporting periodicity |
Ericsson |
| R2-2308690 |
Addition of missing values for dl-prs-ResourceSetPeriodicityReq-r17 |
Samsung |
| R2-2309104 |
Correction to Multi-RTT |
Huawei, HiSilicon |
| R2-2309105 |
LS on the support of multiple location estimate instances in a single measurement report |
RAN2 |
| R2-2309106 |
[AT123][421][POS] dl-prs-ResourceSetPeriodicityReq-r17 range check (Samsung) |
Samsung (Moderator) |
| R2-2309194 |
Addition of missing values for dl-prs-ResourceSetPeriodicityReq-r17 |
Samsung |
| R2-2309294 |
Correction to Multi-RTT |
Huawei, HiSilicon |
| 6.4.2 |
Stage 2 corrections |
|
| R2-2308759 |
Correction of PRU overview description |
Nokia, Nokia Shanghai Bell |
| 6.5.1 |
SON Corrections |
|
| R2-2307705 |
Correction on field sourcePCellId and targetPCellId in TS 38.331 |
CATT |
| R2-2307706 |
Correction on choCandidate and timeSinceCHO-Reconfig logging in SHR |
CATT |
| R2-2308421 |
Correction on logging RLM resources in the RLF report |
Ericsson, Qualcomm |
| R2-2308422 |
Duppliacted PSCell ID logging in the RA report |
Ericsson |
| R2-2308554 |
NB-IoT UE location Info in RLF report |
Qualcomm Incorporated |
| R2-2308555 |
Correction on UE location information in NB-IoT RLF report |
Qualcomm Incorporated |
| R2-2308650 |
Correction on timeSinceCHO-Reconfig in TS 38.331 |
SHARP Corporation |
| R2-2309030 |
LS on user consent for SON/MDT for NB-IoT Ues |
RAN2 |
| 6.5.2 |
MDT Corrections |
|
| R2-2307068 |
Reply LS on the user consent for trace reporting (S3-231398; contact: Huawei) |
SA3 |
| R2-2307075 |
LS on Excess Packet Delay Threshold for MDT (S5-232150; contact: Nokia) |
SA5 |
| R2-2307282 |
Correction to LoggedMeasurementConfiguration type |
Nokia, Nokia Shanghai Bell |
| R2-2308500 |
CR to 37320 on RLF report and CEF report |
ZTE Corporation, Sanechips |
| R2-2308643 |
Correction on delay definitions for split DRB |
Huawei, HiSilicon |
| R2-2308644 |
Discussion on NB-IoT UE location in RLF report |
Huawei, HiSilicon |
| R2-2309029 |
CR to 37320 on RLF report and CEF report |
ZTE Corporation, Sanechips |
| R2-2309279 |
Agreed corrections for Rel-17 SONMDT (Ericsson) |
Ericsson, Nokia and Nokia Shanghai Bell, CATT |
| 6.6 |
NR Sidelink enhancements |
|
| R2-2307098 |
Correction on SIB/Preconfiguration applicability |
OPPO |
| 6.6.1 |
Control plane and stage 2 corrections |
|
| R2-2307483 |
Correction on SUI transmission for sidelink DRX |
ZTE Corporation, Sanechips |
| R2-2307561 |
Miscellaneous corrections for SL enhancements |
Huawei, HiSilicon, OPPO |
| R2-2307939 |
Correction to 38300 on SL DRX |
Ericsson |
| R2-2307980 |
Correction to 38.300 on idle/inactive sidelink UEs |
vivo |
| R2-2307981 |
Correction to 38.331 on IUC |
vivo |
| R2-2308360 |
Correction on usage of sensing results with preferred resource set |
Nokia, Nokia Shanghai Bell |
| R2-2308521 |
Rapporteur Miscellaneous Stage 2 Corrections |
InterDigital France R&D, SAS |
| R2-2308562 |
Summary on RRC corrections for SL enhancements |
Huawei, HiSilicon |
| R2-2309131 |
Summary of [AT123][504][V2X/SL] SL-e 38.300 corrections (InterDigital) |
InterDigital |
| R2-2309132 |
Rapporteur Miscellaneous Stage 2 Corrections |
InterDigital, Ericsson |
| R2-2309133 |
Summary on [AT123][505][V2X/SL] SL-e CP corrections (Huawei) |
Huawei, HiSilicon |
| R2-2309134 |
Miscellaneous corrections for SL enhancements |
Huawei, HiSilicon, OPPO, ZTE Corporation, Sanechips |
| 6.6.2 |
User plane corrections |
|
| R2-2307240 |
Miscellaneous corrections on TS 38.321 for SL enhancements |
OPPO |
| R2-2307571 |
Correction on Inter-UE Coordination Information MAC CE |
Huawei, HiSilicon |
| R2-2307572 |
Corrections on SL DRX |
Huawei, HiSilicon |
| R2-2307721 |
Corrections on SL DRX |
Xiaomi |
| R2-2307722 |
Corrections on IUC MAC CE |
Xiaomi |
| R2-2307752 |
Correction on NR Sidelink MAC |
Philips International B.V. |
| R2-2308367 |
Differentiation between SL DRX configuration and active time specification |
Nokia, Nokia Shanghai Bell |
| R2-2308715 |
MAC corrections for Sidelink |
ASUSTeK |
| R2-2309129 |
Correction on NR Sidelink MAC |
Philips International B.V. |
| R2-2309136 |
[AT123][506][V2X/SL] SL-e 38.321 corrections (Xiaomi) |
Xiaomi |
| R2-2309137 |
Miscellaneous corrections on TS 38.321 for NR sidelink |
Xiaomi, OPPO, Huawei, Nokia, ASUSTeK |
| 7.0.1 |
UE Capabilities |
|
| R2-2307013 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#113 (R1-2306225; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2307021 |
LS on Rel-18 higher-layers parameter list (R1-2306270; contact: Ericsson) |
RAN1 |
| R2-2308086 |
Running UE capability CR on 38.331 for Rel-18 R1 R4 feature lists |
Intel Corporation |
| R2-2308087 |
Running UE capability CR on 38.306 for Rel-18 R1 R4 feature lists |
Intel Corporation |
| R2-2308088 |
Running UE capability CR on 38.822 for Rel-18 R1 R4 feature lists |
Intel Corporation |
| 7.0.2 |
Other |
|
| R2-2308254 |
Rel-18 ASN.1 review plan |
Ericsson |
| 7.1 |
NR network-controlled repeaters |
|
| R2-2307469 |
Missing agreement and clarifications of in-band network-controlled repeater |
NEC |
| R2-2307500 |
Correction on 38.304 on NCR |
Huawei, HiSilicon |
| R2-2307688 |
Miscellaneous Corrections to NCR RRC Running CR |
vivo |
| R2-2308069 |
Introducing support for Network Controlled Repeaters to 38.331 |
ZTE Corporation (Rapporteur) |
| R2-2308095 |
Introducing support for Network Controlled Repeaters to 38.321 |
Samsung |
| R2-2308895 |
RRC corrections for NCR related to security |
Samsung Electronics Czech |
| R2-2308910 |
Small corrections for NCR |
Ericsson |
| R2-2308911 |
Correction on periodicity for NCR beam configuration |
Ericsson |
| R2-2309051 |
Introducing support for Network Controlled Repeaters to 38.331 |
ZTE Corporation (Rapporteur) |
| R2-2309052 |
Introducing support for Network Controlled Repeaters to 38.321 |
Samsung |
| R2-2309053 |
Small corrections for NCR |
Ericsson |
| 7.2.1 |
Organizational |
|
| R2-2307004 |
LS reply on the RAT-dependent positioning integrity (R1-2306157; contact: InterDigital) |
RAN1 |
| R2-2307007 |
Reply LS on Sidelink positioning procedure (R1-2306208; contact: Xiaomi) |
RAN1 |
| R2-2307010 |
LS to RAN2 on SRS bandwidth aggregation for positioning (R1-2306214; contact: ZTE) |
RAN1 |
| R2-2307031 |
Reply LS on Authorization and Provisioning for Ranging/SL positioning service (R3-233424; contact: Xiaomi) |
RAN3 |
| R2-2307032 |
Reply LS on SRS Configuration Request (R2-2302278; contact: Huawei) |
RAN3 |
| R2-2307042 |
LS on reporting granularity for timing related positioning measurements (R4-2310166; contact: Huawei) |
RAN4 |
| R2-2307052 |
Reply LS on the requirement on low power or high accuracy positioning (S1-231370; contact: Huawei) |
SA1 |
| R2-2307054 |
Reply LS to LS to SA2 on Sidelink positioning procedure (S2-2305735; contact: Xiaomi) |
SA2 |
| R2-2307056 |
LS on assistance information provided to UE (S2-2307553; contact: Xiaomi) |
SA2 |
| R2-2307124 |
Running MAC CR for LPHAP |
Huawei, HiSilicon |
| R2-2307125 |
Running MAC CR for Sidelink Positioning |
Huawei, HiSilicon |
| R2-2307126 |
Draft reply LS on timing measurement reporting granularity |
Huawei, HiSilicon |
| R2-2307127 |
Discussion on measurement reporting granularity |
Huawei, HiSilicon |
| R2-2307391 |
LPP running CR for RAT-dependent integrity |
CATT |
| R2-2307662 |
Further considerations on SLPP specification |
Intel Corporation |
| R2-2307663 |
TS 38.355 v0.0.4 |
Intel Corporation |
| R2-2308053 |
Discussion on the reply LSs to SA2 on SL Positioning |
OPPO |
| R2-2308139 |
[draft]Reply LS to RAN1 on SRS bandwidth aggregation for positioning |
ZTE Corporation |
| R2-2308259 |
Discussion on R18 positioning UE capabilities |
Xiaomi |
| R2-2308385 |
Running Stage 2 CR for 'Expanded and improved NR positioning' |
Qualcomm Incorporated |
| R2-2308386 |
Stage 2 TP for SL-MO-LR/SL-MT-LR |
Qualcomm Incorporated |
| R2-2308387 |
Stage 2 TP for SLPP Transport between UE and LMF |
Qualcomm Incorporated |
| R2-2308395 |
Stage 2 TP for SLPP Transport between UEs |
Qualcomm Incorporated |
| R2-2308484 |
Rapporteur CR for Positioning RRC Changes |
Ericsson |
| R2-2308946 |
Draft reply LS on timing measurement reporting granularity |
Huawei, HiSilicon |
| R2-2308947 |
Discussion on measurement reporting granularity |
Huawei, HiSilicon |
| R2-2309117 |
Reply LS on SRS bandwidth aggregation for positioning |
RAN2 |
| R2-2309118 |
Draft reply LS on timing measurement reporting granularity |
Huawei, HiSilicon |
| R2-2309175 |
[AT123][410][POS] Rel-18 positioning capabilities |
Xiaomi |
| R2-2309176 |
Summary of [AT123][403][POS] LS to RAN4 on timing measurement reporting granularity (Huawei) |
Huawei, HiSilicon |
| R2-2309177 |
Summary of [AT123][404][POS] LS(s) to SA2 on sidelink positioning (Xiaomi) |
Xiaomi |
| R2-2309179 |
Running MAC CR for LPHAP |
Huawei, HiSilicon |
| R2-2309180 |
Running MAC CR for Sidelink Positioning |
Huawei, HiSilicon |
| R2-2309181 |
LPP running CR for RAT-dependent integrity |
CATT |
| R2-2309182 |
Rapporteur CR for Positioning RRC Changes |
Ericsson |
| R2-2309183 |
TS 38.355 v0.0.5 |
Intel Corporation |
| R2-2309207 |
Running Stage 2 CR for 'Expanded and improved NR positioning' |
Qualcomm Incorporated |
| R2-2309227 |
[AT123][409][POS] TS 38.355 (Intel) |
Intel Corporation |
| R2-2309229 |
Summary of [AT123][405][POS] Rel-18 positioning MAC CRs (Huawei) |
Huawei, HiSilicon |
| R2-2309232 |
[AT123][406][POS] Rel-18 LPP CR on RAT-dependent integrity (CATT) |
CATT |
| R2-2309305 |
Draft running MAC CR for the introduction of Sidelink Positioning |
Huawei, HiSilicon |
| R2-2309306 |
Summary of [Post123][414][POS] Rel-18 positioning MAC CRs (Huawei) |
Huawei, HiSilicon |
| 7.2.2 |
Sidelink positioning |
|
| R2-2307122 |
Discussion on higher layer aspects for Sidelink Positioning |
Huawei, HiSilicon |
| R2-2307123 |
Discussion on lower layer aspects for Sidelink Positioning |
Huawei, HiSilicon |
| R2-2307185 |
UE Positioning using Sidelink in OoC |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2307187 |
Preconfigured Assistance Data for UE Positioning in Hybrid Uu and PC5 scenarios |
Fraunhofer IIS, Fraunhofer HHI, Ericsson |
| R2-2307232 |
Discussion of SLPP / LPP signalling procedures |
Nokia Netherlands |
| R2-2307241 |
Discussion of session-less and session-based positioning |
Nokia Netherlands |
| R2-2307340 |
SLPP signalling in UE-only sidelink positioning/ranging procedure |
MediaTek Inc. |
| R2-2307341 |
Pathological cases of network-based operation for sidelink positioning |
MediaTek Inc. |
| R2-2307392 |
Discussion on sidelink positioning |
CATT |
| R2-2307426 |
Discussion on sidelink positioning |
vivo |
| R2-2307507 |
Discussion on SL positioning |
Xiaomi |
| R2-2307660 |
Report of [ 402] SLPP session handling |
Intel Corporation |
| R2-2307661 |
Further considerations on sidelink positioning |
Intel Corporation |
| R2-2307778 |
SLPP design for session aspects |
Samsung Electronics Romania |
| R2-2307823 |
SL positioning procedures |
Apple |
| R2-2308052 |
Further discussion on sidelink positioning |
OPPO |
| R2-2308125 |
Discussion on sidelink positioning |
Spreadtrum Communications |
| R2-2308138 |
Discussion on sidelink positioning |
ZTE Corporation |
| R2-2308152 |
Considerations on sidelink positioning resources |
Sony |
| R2-2308276 |
Discussion on SL Positioning |
Lenovo |
| R2-2308284 |
Discussion on sidelink positioning |
ROBERT BOSCH GmbH |
| R2-2308316 |
Considerations on Sidelink positioning |
CMCC |
| R2-2308384 |
Discussion on sidelink positioning |
InterDigital, Inc. |
| R2-2308396 |
Sidelink Positioning Protocol (SLPP) Signaling and Procedures |
Qualcomm Incorporated |
| R2-2308416 |
Pathological cases of network-based operation for sidelink positioning |
MediaTek Inc., CATT |
| R2-2308480 |
Sidelink positioning |
Ericsson |
| R2-2308557 |
Discussion of resource allocation aspects |
Nokia Netherlands |
| R2-2308595 |
Discussion on higher layer aspects for sidelink positioning |
LG Electronics Inc. |
| R2-2308600 |
Discussion on lower layer aspects for sidelink positioning |
LG Electronics Inc. |
| R2-2308657 |
Discussion on priority value for SL-PRS |
Samsung Electronics Co., Ltd |
| R2-2308800 |
Further Discussions on Sidelink Positioning & Ranging |
CEWiT |
| R2-2308884 |
Discussion on Anchor UE discovery and selection in sidelink positioning |
KT Corp. |
| R2-2308908 |
On the selection of Anchor UEs for Sidelink Positioning |
Philips International B.V. |
| R2-2308935 |
On the support of UE-only SL positioning in in-coverage and partial coverage scenarios |
Philips International B.V. |
| R2-2308973 |
[Pre123][402][POS] Summary of AI 7.2.2 sidelink positioning (CATT) |
CATT |
| R2-2309171 |
[AT123][429][POS] UEs without connection to LMF and SLPP forwarding (Apple) |
Apple (Moderator) |
| R2-2309172 |
[AT123][430][POS] Discovery and selection for sidelink positioning (CATT) |
CATT |
| R2-2309173 |
Summary of [AT123][431][POS] Sidelink Positioning MAC issues (Huawei) |
Huawei, HiSilicon |
| R2-2309304 |
LS on SL positioning MAC agreements |
RAN2 |
| R2-2309343 |
LS on SL positioning MAC agreements |
RAN2 |
| 7.2.3 |
RAT-dependent integrity |
|
| R2-2307393 |
Discussion on RAT-Dependent integrity |
CATT |
| R2-2307427 |
Remaining issues of RAT-dependent integrity |
vivo |
| R2-2307664 |
Further considerations on RAT dependent integrity |
Intel Corporation |
| R2-2307999 |
Discussion on RAT-dependent integrity |
Lenovo |
| R2-2308050 |
Consideration on RAT-dependent positioning integrity |
OPPO |
| R2-2308136 |
Discussion on RAT-dependent methods positioning integrity |
ZTE Corporation |
| R2-2308260 |
Discussion on RAT-dependent positioning integrity |
Xiaomi |
| R2-2308397 |
Integrity of NR Positioning Technologies |
Qualcomm Incorporated |
| R2-2308482 |
On RAT-dependent positioning Integrity |
Ericsson |
| R2-2308616 |
Discussion on RAT dependent integrity |
InterDigital, Inc. |
| 7.2.4 |
LPHAP |
|
| R2-2307121 |
Discussion on LPHAP |
Huawei, HiSilicon |
| R2-2307186 |
Enhancements for supporting LPHAP |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2307394 |
Discussion on SRS configuration with validity area and alignment between PRS and (e)DRX |
CATT |
| R2-2307428 |
Discussion on solution of LPHAP |
vivo |
| R2-2307665 |
Further considerations on LPHAP |
Intel Corporation |
| R2-2307824 |
Alignment between DRX and PRS |
Apple |
| R2-2308000 |
Discussion on low power high accuracy positioning |
Lenovo |
| R2-2308051 |
Discussion on LPHAP enhancement |
OPPO |
| R2-2308126 |
Discussion on LPHAP |
Spreadtrum Communications |
| R2-2308135 |
Discussion on LPHAP |
ZTE Corporation |
| R2-2308153 |
Considerations on Low Power High Accuracy Positioning |
Sony |
| R2-2308261 |
Discussion on LPHA positioning |
Xiaomi |
| R2-2308317 |
Further considerations on LPHAP |
CMCC |
| R2-2308398 |
Enhancements for LPHAP |
Qualcomm Incorporated |
| R2-2308481 |
Discussion on Low Power High Accuracy Positioning |
Ericsson |
| R2-2308618 |
Discussion on LPHAP |
InterDigital, Inc. |
| R2-2308693 |
Discussion on alignment between (e)DRX and PRS |
Samsung |
| R2-2308694 |
Discussion on SRS configuration in RRC_INACTIVE |
Samsung |
| R2-2308812 |
Report of [Post122][401][POS] SRS configuration and activation in LPHAP (CATT) |
CATT |
| R2-2308959 |
Summary for 7.2.4 LPHAP excluding SRS configuration & activation part |
OPPO (Rapporteur) |
| 7.2.5 |
RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
|
| R2-2307395 |
Discussion on carrier phase positioning, bandwidth aggregation for positioning and Redcap positioning |
CATT |
| R2-2307429 |
RAN2-related issues about bandwidth aggregation |
vivo |
| R2-2307455 |
Discussion on RAN1 led positioning topics |
Huawei, HiSilicon |
| R2-2307666 |
Considerations on other RAN1 led items |
Intel Corporation |
| R2-2307827 |
On-demand PRS with bandwidth aggregation |
Apple |
| R2-2308001 |
Discussion on RedCap positioning, carrier phase positioning and PRS/SRS bandwidth aggregation |
Lenovo |
| R2-2308137 |
Discussion on BW aggregation and RedCap positioning |
ZTE Corporation |
| R2-2308174 |
Discussion on Frequency hopping for Positioning for RedCap Ues |
Sony |
| R2-2308262 |
Discussion on RedCap positioning, carrier phase positioning and bandwidth aggregation for positioning |
Xiaomi |
| R2-2308399 |
Configuration Enhancements for DL-PRS Aggregation |
Qualcomm Incorporated |
| R2-2308483 |
Discussion based upon RAN1 agreements on CPP, RedCap, Bandwidth aggregation |
Ericsson |
| R2-2308619 |
Discussion on positioning for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning |
InterDigital, Inc. |
| R2-2308761 |
Assessment of impact of carrier phase positioning on higher layer protocols |
Nokia, Nokia Shanghai Bell |
| 7.3.1 |
Organizational |
|
| R2-2307017 |
Reply LS on Cell DTX/DRX activation/deactivation (R1-2306246; contact: Huawei, Intel) |
RAN1 |
| R2-2307053 |
Reply LS on 3GPP work on Energy Efficiency (S1-231805; contact: Nokia) |
SA1 |
| R2-2307063 |
Reply LS on the enhancements to restricting paging in a limited area (S2-2307984; contact: Qualcomm) |
SA2 |
| R2-2307073 |
LS on 3GPP work on Energy Efficiency (S4-231111; contact: Qualcomm) |
SA4 |
| R2-2307528 |
Running 38.331 CR - Introduction of Network energy savings for NR |
Huawei, HiSilicon |
| R2-2308044 |
Work plan for NR network energy savings |
Huawei, HiSilicon |
| R2-2308393 |
Running CR to 38.321 for Network Energy Savings |
InterDigital |
| R2-2308394 |
TS 38.321 open issues for NES |
InterDigital |
| R2-2308492 |
Running CR to 38300 for Network energy savings |
Ericsson |
| R2-2309313 |
Running CR to 38300 for Network energy savings |
Ericsson |
| R2-2309346 |
Running CR to 38300 for Network energy savings |
Ericsson |
| 7.3.2 |
DTX/DRX mechanism |
|
| R2-2307147 |
Joint Operation between UE C-DRX and Cell DTX |
NEC |
| R2-2307150 |
Discussion on Cell DTX/DRX configuration and operation |
Xiaomi |
| R2-2307177 |
Remaining issues for Cell DTX_DRX |
Samsung Electronics Co., Ltd |
| R2-2307178 |
Various (RRC Procedure, Measurement, SR, CG etc.) alignment aspects |
Lenovo |
| R2-2307524 |
Discussion on cell DTX and DRX |
Huawei, HiSilicon |
| R2-2307527 |
Outcome of [Post122][307][NES] DTX/DRX – alignment, single/multiple configurations, parameter values (Huawei) |
Huawei, HiSilicon |
| R2-2307647 |
Cell DTX-DRX Mechanism |
Qualcomm Incorporated |
| R2-2307713 |
Cell DTX/DRX NES Techniques |
III |
| R2-2307717 |
Discussion on cell DTX/DRX |
KDDI Corporation |
| R2-2307760 |
SPS/CG and MAC CE Activation/Deactivation in Cell DTX/DRX |
Samsung |
| R2-2307787 |
Remaining issues on Cell DTX/DRX |
Nokia, Nokia Shanghai Bell |
| R2-2307808 |
Discussion on key issues of Cell DTX/DRX |
Apple |
| R2-2307897 |
TAT aspects under Cell-DTX/Cell-DRX |
FGI |
| R2-2307898 |
Discussion on cell DTX and DRX |
FGI |
| R2-2307911 |
Single configuration with multiple DTX_DRX patterns and explicit signalling |
BT Plc, Nokia, T-Mobile, Deutsche Telekom, NTT Docomo, KDDI, ZTE |
| R2-2308179 |
Discussion on DTX/DRX mechanism |
OPPO |
| R2-2308279 |
The remaining issues on cell DTX and DRX |
ZTE corporation, Sanechips |
| R2-2308301 |
Discussion on cell DTXDRX |
CMCC |
| R2-2308388 |
Remaining issues on Cell DTX/DRX |
InterDigital |
| R2-2308448 |
UL considerations for Cell DTX/DRX |
NEC Telecom MODUS Ltd. |
| R2-2308493 |
Further aspects on cell DTX/DRX |
Ericsson |
| R2-2308534 |
Cell DTX/DRX traffic adaptations |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2308593 |
Discussion on DTX/DRX mechanism |
LG Electronics Inc. |
| R2-2308606 |
Discussion on Cell DTX/DRX |
Fujitsu |
| R2-2308703 |
Support multiple configuration of Cell DTX/DRX |
ETRI |
| R2-2308727 |
Leftover issues of Cell DTX/DRX |
CATT, Turkcell |
| R2-2308737 |
Remaining issues for cell DTX-DRX |
vivo |
| R2-2308738 |
UE C-DRX configuration used upon cell DTX activation |
vivo, Fraunhofer IIS, Huawei, HiSilicon, LG Electronics Inc., MediaTek Inc., NEC, Xiaomi |
| R2-2308794 |
Further aspects on cell DTX/DRX |
Ericsson |
| R2-2308886 |
Cell DTX/DRX NES Techniques |
CEWiT |
| 7.3.3 |
SSB-less Scell operation |
|
| R2-2307152 |
Discussion on inter-band SSB-less SCell |
Xiaomi |
| R2-2307519 |
On NES SSB-less SCell operation |
Nokia, Nokia Shanghai Bell |
| R2-2307648 |
SSB-less Interband CA |
Qualcomm Incorporated |
| R2-2307810 |
Further Discussion on RAN2 work of inter-band SSB-less CA |
Apple |
| R2-2308026 |
Discuss on SSB-less SCell operation in NES |
Lenovo |
| R2-2308180 |
Discussion on SSB-less Scell operation |
OPPO |
| R2-2308280 |
Discussion on SSB-less SCell operation for NES |
ZTE corporation, Sanechips |
| R2-2308359 |
On SBB/SIB-less NES solutions |
Dell Technologies |
| R2-2308391 |
SSB-less Scell operation |
InterDigital |
| R2-2308728 |
Enhancements on SSB-less SCell operation |
CATT |
| 7.3.4 |
Cell selection/re-selection |
|
| R2-2307149 |
Discussion on RRC_IDLE/INACTIVE UE behavior due to NES |
Xiaomi |
| R2-2307220 |
Discussion on cell selection and reselection for NES |
Samsung Electronics GmbH |
| R2-2307525 |
Discussion on cell selection/reselection for NES |
Huawei, HiSilicon |
| R2-2307765 |
Reselection and Paging handling for NES |
Nokia, Nokia Shanghai Bell |
| R2-2307809 |
Detailed mechanism of legacy UE barring in NES cell |
Apple |
| R2-2308027 |
Cell selection/re-selection in NES |
Lenovo |
| R2-2308181 |
Discussion on cell selection reselection |
OPPO |
| R2-2308281 |
Consideration on cell selection and reselection enhancements for NES |
ZTE corporation, Sanechips |
| R2-2308333 |
Discussion on cell barring and reselection for NES |
CMCC |
| R2-2308389 |
Cell selection and resection for NES |
InterDigital |
| R2-2308449 |
Procedure for legacy UEs camping on NES cells |
NEC Telecom MODUS Ltd. |
| R2-2308494 |
Remaining aspects for NES Cell selection/reselection |
Ericsson |
| R2-2308533 |
Cell Selection and Re-Selection for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2308681 |
Access restriction |
LG Electronics |
| R2-2308729 |
Consideration on Cell Selection/Re-selection on NES cells |
CATT |
| R2-2308739 |
Discussion on cell selection/re-selection |
vivo |
| R2-2308784 |
Access restrition for NES |
LG Electronics Inc. |
| R2-2308831 |
Discussion on Cell selection |
NTT DOCOMO INC. |
| 7.3.5 |
Connected mode mobility |
|
| R2-2307151 |
Discussion on UE mobility due to NES cell |
Xiaomi |
| R2-2307179 |
CHO Procedure in NES Mode |
Lenovo |
| R2-2307221 |
Discussion on Connected mode mobility for NES |
Samsung Electronics GmbH |
| R2-2307456 |
Discussion on CHO for NES |
Ericsson |
| R2-2307475 |
Discussion on the CHO Enhancements for NES |
Google Inc. |
| R2-2307645 |
Discussion on CHO enhancement |
NEC |
| R2-2307649 |
NES Connected mode mobility |
Qualcomm Incorporated |
| R2-2307766 |
CHO on NES |
Nokia, Nokia Shanghai Bell |
| R2-2307811 |
Further Discussion on CHO enhancement in NES |
Apple |
| R2-2307917 |
Discussion on CHO enhancements for NES |
Sharp |
| R2-2308031 |
Discussion on CHO enhancement for NES |
Huawei, Turkcell, HiSilicon |
| R2-2308175 |
Handover enhancement for NES |
Sony |
| R2-2308182 |
Discussion on connected mode mobility |
OPPO |
| R2-2308198 |
CHO enhancement for NES cell |
Quectel |
| R2-2308282 |
The remaining issues on connected mode mobility |
ZTE corporation, Sanechips |
| R2-2308302 |
Discussion on connected mode mobility |
CMCC |
| R2-2308390 |
CHO for NES |
InterDigital |
| R2-2308608 |
Discussion on Connected mode mobility for network energy savings |
Fujitsu |
| R2-2308697 |
CHO enhancement for different NES use cases |
LG Electronics Inc. |
| R2-2308730 |
CHO procedure enhancements |
CATT |
| R2-2308740 |
Conditional handover enhancement for network energy saving |
vivo |
| R2-2309211 |
Report of offline discussion on NES specific CHO |
Huawei, HiSilicon |
| 7.3.6 |
Others |
|
| R2-2307458 |
MAC CE for activating/deactivating SP CSI report configurations for NES |
Ericsson |
| R2-2307650 |
Restricting Paging to limited area |
Qualcomm Incorporated |
| R2-2308045 |
Discussion on RAN1 and RAN3 led NES techniques |
Huawei, HiSilicon |
| R2-2308154 |
Skip monitoring of CSI-RS during non-active periods |
Sony |
| 7.4.1 |
Organizational |
|
| R2-2307020 |
LS on beam application time, contents of cell switch command, TCI state activation and UE based TA measurement for LTM (R1-2304276; contact: Fujitsu, MediaTek, CATT) |
RAN1 |
| R2-2307070 |
LS on Security Solution for Selective SCG (S3-233200; contact: Nokia) |
SA3 |
| R2-2307207 |
RRC Running CR for CHO with candidate SCGs |
CATT |
| R2-2307372 |
37.340 running CR for introduction of NR further mobility enhancements |
ZTE Corporation, Sanechips |
| R2-2307388 |
Discussion on replying to the RAN1 LS on beam application time for LTM |
Fujitsu, CATT, MediaTek |
| R2-2307389 |
[Draft] Reply LS on beam application time for LTM |
Fujitsu, CATT, MediaTek |
| R2-2307961 |
38.321 running CR for introduction of NR further mobility enhancements |
Huawei, HiSilicon |
| R2-2308040 |
RRC running CR for subsequent CPAC in NR-DC |
OPPO |
| R2-2308145 |
38.300 running CR for introduction of NR further mobility enhancements |
MediaTek Inc. |
| R2-2308435 |
RRC running CR for LTM |
Ericsson |
| R2-2308436 |
RRC open issues list for LTM |
Ericsson |
| R2-2309224 |
[Draft] Reply LS on beam application time for LTM |
Fujitsu, CATT, MediaTek |
| R2-2309250 |
Reply LS on beam application time for LTM |
RAN2 |
| R2-2309265 |
[draft] LS on RAN2 progress on LTM |
Huawei, HiSilicon |
| R2-2309281 |
38.321 running CR for introduction of NR further mobility enhancements |
Huawei, HiSilicon |
| R2-2309288 |
LS on RAN2 progress on LTM |
RAN2 |
| R2-2309319 |
RRC running CR for CHO with candidate SCGs |
CATT |
| R2-2309325 |
RRC running CR for subsequent CPAC in NR-DC |
OPPO |
| R2-2309335 |
38.300 running CR for introduction of NR further mobility enhancements |
MediaTek Inc., vivo |
| R2-2309336 |
RRC running CR for subsequent CPAC in NR-DC |
OPPO |
| 7.4.2.1 |
General and Stage-2 |
|
| R2-2307137 |
L1 Measurement to support LTM |
NEC |
| R2-2307138 |
Failure handling for L1/L2 triggered mobility |
NEC |
| R2-2307139 |
RACH less LTM cell switch |
NEC |
| R2-2307168 |
Open issues for Early Timing Advance Management for LTM |
Samsung Electronics Co., Ltd |
| R2-2307181 |
Initial Early TA acquisition |
Lenovo |
| R2-2307208 |
Remaining Issues on RACH-less LTM |
CATT |
| R2-2307222 |
On scenarios for LTM |
CATT |
| R2-2307290 |
Discussion on Early TA acquisition and LTM procedure |
vivo |
| R2-2307379 |
On UE based TA measurement and RACH-less LTM |
Futurewei |
| R2-2307396 |
RAN2 aspects of RACH-based early TA acquisition |
Fujitsu |
| R2-2307445 |
Discussion on LTM failure handling |
DOCOMO Beijing Labs |
| R2-2307611 |
Supported scenarios and stage 2 latency description |
Huawei, HiSilicon |
| R2-2307612 |
RACH-less LTM and early TA acquisition |
Huawei, HiSilicon |
| R2-2307667 |
LTM failure recovery |
LG Electronics |
| R2-2307670 |
Remaining issues of RACH-less LTM and early TA |
Xiaomi |
| R2-2307781 |
Discussion on LTM failure handling |
DOCOMO Beijing Labs |
| R2-2307863 |
RSTD based early TA acquisition |
Apple |
| R2-2307888 |
Discussion the remaining issues for LTM early TA acquisition |
ITRI |
| R2-2307985 |
Miscellaneous issues of L1/L2 Triggered Mobility |
Rakuten Symphony |
| R2-2307987 |
Delayed Resource Reservation for inter gNB-DU LTM |
Rakuten Symphony |
| R2-2307988 |
Prioritizing of LTM candidate cells |
Rakuten Symphony |
| R2-2308003 |
Re-acquisition and forwarding of early TA |
Lenovo |
| R2-2308036 |
Security impacts of intra gNB, inter gNB-CU-UP relocation |
Rakuten Symphony |
| R2-2308037 |
Discussion on early sync and RACH-less for LTM |
OPPO |
| R2-2308096 |
Fast cell recovery operations for LTM failures |
PANASONIC |
| R2-2308149 |
RACH-Less LTM and Early TA Acquisition |
MediaTek Inc. |
| R2-2308172 |
RACH-less solution and TA indication for LTM |
Sony |
| R2-2308213 |
Discussion on open issues of RACH-less LTM cell switch |
Transsion Holdings |
| R2-2308318 |
Considerations on failure handling |
CMCC |
| R2-2308319 |
Discussions on LTM open issues |
CMCC |
| R2-2308438 |
Signalling approaches for LTM cell switch execution |
Ericsson |
| R2-2308439 |
Stage-2 proposal on early sync for LTM |
Ericsson |
| R2-2308572 |
RRC_INACTIVE and LTM |
Interdigital, Inc. |
| R2-2308573 |
LTM execution upon RLF and HOF |
Interdigital, Inc. |
| R2-2308614 |
LTM procedures |
Qualcomm Incorporated |
| R2-2308840 |
Further Considerations on RACH procedure for early TA acquisiton |
ZTE Corporation, Sanechips |
| R2-2308888 |
Further details on TA acquisition and maintenance in LTM |
Nokia, Nokia Shanghai Bell |
| R2-2308918 |
Discussions on LTM related measurements |
CMCC |
| R2-2309248 |
Reply LS on Approaches during execution for inter-DU LTM |
Ericsson |
| R2-2309251 |
Reply LS on Approaches during execution for inter-DU LTM |
RAN2 |
| 7.4.2.2 |
RRC |
|
| R2-2307223 |
Discussion on RRC aspects for LTM |
CATT |
| R2-2307291 |
RRC configuration for LTM |
vivo |
| R2-2307373 |
Remaining issues on LTM RRC |
ZTE Corporation, Sanechips |
| R2-2307380 |
Configuration for sequential measurement and UE based RACH-less LTM |
Futurewei |
| R2-2307382 |
Open Issues for LTM RRC |
MediaTek Inc. |
| R2-2307390 |
Failure detection and fast recovery |
Fujitsu |
| R2-2307397 |
RRC aspects of L1/L2 triggered mobility |
Fujitsu |
| R2-2307576 |
On Validity Check for LTM Configuration |
Nokia, Nokia Shanghai Bell |
| R2-2307577 |
On Reference, Delta, Subsequent LTM and L3 Mobility |
Nokia, Nokia Shanghai Bell |
| R2-2307610 |
RRC aspects for LTM |
Huawei, HiSilicon |
| R2-2307642 |
Further discussion on cell switch |
NEC |
| R2-2307643 |
Discussion on RAN3 related issues |
NEC |
| R2-2307668 |
Discussion on LTM RRC configuration |
LG Electronics |
| R2-2307669 |
Remaining issues of RRC configured Layer-2 reset |
Xiaomi |
| R2-2307714 |
Remaining issues for RRC Aspects of LTM |
Sharp |
| R2-2307883 |
Enhancing the L2 reset signalling in LTM |
Apple |
| R2-2307886 |
LTM cell switch link failure handling |
Apple |
| R2-2308004 |
RRC issues for LTM |
Lenovo |
| R2-2308038 |
Discussion on RRC open issues for LTM |
OPPO |
| R2-2308123 |
Discussion on the remaining RRC aspects for LTM |
Spreadtrum Communications |
| R2-2308214 |
Discussion on remaining issues of measurement for LTM |
Transsion Holdings |
| R2-2308434 |
[Post122][055][Mob18] Discussion on RRC open issues list for LTM |
Ericsson |
| R2-2308437 |
Discussion of remaining RRC open issues for LTM |
Ericsson |
| R2-2308440 |
Handling of SCells and SCG during LTM cell switch |
Ericsson |
| R2-2308441 |
LTM handling for fast recovery and RRC Re-establishment |
Ericsson |
| R2-2308574 |
RRC Measurements when LTM is Configured |
Interdigital, Inc. |
| R2-2308575 |
RLC and PDCP reset |
Interdigital, Inc. |
| R2-2308613 |
Conflict between LTM triggering and legacy RRC messaging |
Qualcomm Incorporated |
| R2-2308615 |
RRC aspects of LTM |
Qualcomm Incorporated |
| R2-2308685 |
Remaining Issues and Security concern alleviation of Cell Switch command |
LG Electronics |
| R2-2308813 |
Discussion on L1 measurement RS configuration |
Google Inc. |
| R2-2308818 |
Discussion on RRC aspects for L1/L2-Triggered Mobility |
Xiaomi |
| R2-2308829 |
Discussion on LTM reference configuration |
Google Inc. |
| R2-2308866 |
Discussion on RRC aspects of LTM |
Samsung |
| R2-2309249 |
[AT123][015][Mob18] RRC centric offline |
Ericsson |
| 7.4.2.3 |
L2 centric parts |
|
| R2-2307169 |
TAT and TCI state handling upon cell switching |
Samsung Electronics Co., Ltd |
| R2-2307180 |
Cell Switch details |
Lenovo |
| R2-2307209 |
Discussion on L2 Centric Parts |
CATT |
| R2-2307289 |
Remaining issues on dynamic cell switch |
vivo |
| R2-2307381 |
Support UE based RACH-less LTM at lower layer |
Futurewei |
| R2-2307398 |
LTM cell switch execution and completion |
Fujitsu |
| R2-2307671 |
Clarification on the TCI state indicated in the LTM MAC CE |
Xiaomi |
| R2-2307687 |
Discussions on remaining issues for RACH-less LTM |
KDDI Corporation |
| R2-2307697 |
Beam handling and security issue on cell switch for LTM |
Samsung |
| R2-2307884 |
CFRA and CG configuration aspects in LTM |
Apple |
| R2-2307887 |
TCI state operations for LTM |
Panasonic |
| R2-2307962 |
Summary of [Post122][058][Mob18] Contents of Cell Switch MAC CE |
Huawei, HiSilicon |
| R2-2307963 |
Leftovers related LTM MAC CE and cell switch |
Huawei, HiSilicon |
| R2-2307986 |
TA Acquisition before LTM Serving cell change |
Rakuten Symphony |
| R2-2308039 |
Discussion on CG based first UL transmmission for RACH-less LTM |
OPPO |
| R2-2308147 |
Remaining issues for The Contents of LTM MAC CE |
Sharp |
| R2-2308215 |
Discussion on open issues for LTM |
Transsion Holdings |
| R2-2308320 |
Considerations on cell switch |
CMCC |
| R2-2308612 |
Approaches for inter-DU LTM cell switch |
Qualcomm Incorporated |
| R2-2308716 |
Discussion on fallback RACH for L1L2-triggered mobility |
ASUSTeK |
| R2-2308745 |
Discussion on BWP operation by PDCCH-order based RACH for a candidate cell |
LG Electronics Inc. |
| R2-2308841 |
Further Discussion on RACH-less LTM execution |
ZTE Corporation, Sanechips |
| R2-2308887 |
On the cell switch in LTM |
Nokia, Nokia Shanghai Bell |
| R2-2309247 |
Report of Offline Discussion [016] for Early TA Acquisition and RACH-Less |
ZTE Corporation |
| 7.4.3 |
NR-DC with selective activation cell of groups |
|
| R2-2307210 |
Discussion on Selective Activation of Cell Groups in NR-DC |
CATT |
| R2-2307292 |
Discussion on security aspects for selective SCG based on SA3 reply LS |
vivo |
| R2-2307293 |
Remaining issues for NR-DC with selective activation cell of groups |
vivo |
| R2-2307374 |
Remaining issues on subsequent CPAC |
ZTE Corporation, Sanechips |
| R2-2307375 |
Preparation procedure for subsequent CPAC |
ZTE Corporation, Sanechips |
| R2-2307407 |
Discussion on NR-DC with subsequent CPAC. |
DENSO CORPORATION |
| R2-2307613 |
Subsequent CPAC |
Huawei, HiSilicon |
| R2-2307644 |
Further details on subsequent CPAC |
NEC |
| R2-2307683 |
Discussion on subsequent CPAC |
NTT DOCOMO, INC. |
| R2-2307698 |
Considerations on Subsequent CPAC after SCG Change |
Samsung |
| R2-2307715 |
Discussion on NR-DC with selective activation cell of groups |
KDDI Corporation |
| R2-2307771 |
Further analysis on S-CPAC signalling procedures, Configurations and security issues |
Nokia, Nokia Shanghai Bell |
| R2-2307786 |
SCG Selective Activation in NR-DC |
Qualcomm Incorporated |
| R2-2307864 |
Discussion on Subsequent CPAC |
Apple |
| R2-2307885 |
RAN2 impacts from SA3 security key reuse solutions |
Apple |
| R2-2307889 |
Discussion on the evaluation adjustment for SCPAC |
ITRI |
| R2-2307890 |
Discussion on SCG failure handling with subsequent CPAC |
ITRI |
| R2-2307971 |
Subsequent CPAC |
Ericsson |
| R2-2308002 |
Left issues on subsequent CPAC |
Lenovo |
| R2-2308041 |
Discussion on execution condition for subsequent CPAC |
OPPO |
| R2-2308042 |
Open issues for subsequent CPAC in NR-DC |
OPPO |
| R2-2308121 |
Discussion on issues of subsequent CPAC |
Spreadtrum Communications |
| R2-2308148 |
Remaining issues for Subsequent CPAC |
Sharp |
| R2-2308216 |
Discussion on Selective Activation of Cell Groups in NR-DC |
Transsion Holdings |
| R2-2308287 |
Discussion on NR-DC with selective activation of cell groups |
CMCC |
| R2-2308408 |
Subsequent change of SCGs and selective activation |
Interdigital Inc. |
| R2-2308563 |
Subsequent change of SCGs and selective activation |
Interdigital Inc. |
| R2-2308756 |
Discussion on subsequent CPAC |
MediaTek Inc. |
| R2-2308785 |
Subsequent CPC in NR |
LG Electronics |
| R2-2308819 |
Discussion on subsequent CPAC |
Xiaomi |
| R2-2309246 |
[DRAFT] Reply LS on security for selective SCG activation. |
Nokia |
| R2-2309257 |
[AT123][028][Mob18] Understanding of MN-initiated and SN-initiated case (OPPO) |
OPPO |
| R2-2309268 |
Reply LS on security for selective SCG activation. |
RAN2 |
| 7.4.4 |
CHO including target MCG and candidate SCGs for CPC CPA in NR-DC |
|
| R2-2307211 |
Report of [Post122][057][Mob18] 38.331 Running CR for CHO with candidate SCGs |
CATT |
| R2-2307212 |
Discussion on CHO with candidate SCGs |
CATT |
| R2-2307294 |
Discussion on CHO with candidate SCGs |
vivo |
| R2-2307376 |
Discussion on CHO with candidate SCG(s) |
ZTE Corporation, Sanechips |
| R2-2307578 |
Further details on CHO with CPAC in Rel-18 |
Nokia, Nokia Shanghai Bell |
| R2-2307785 |
CHO with multiple candidate SCGs |
Qualcomm Incorporated |
| R2-2307900 |
Discussion on CHO with candidate SCG |
FGI |
| R2-2307964 |
Discussion on CHO with candidate SCG(s) |
Huawei, HiSilicon |
| R2-2307972 |
CHO with associated CPC or CPA |
Ericsson |
| R2-2308005 |
CHO with candidate SCG for CPAC |
Lenovo |
| R2-2308043 |
Discussion on open issues for CHO with candidate SCGs |
OPPO |
| R2-2308122 |
Discussion on CHO with CPAC in NR-DC |
Spreadtrum Communications |
| R2-2308226 |
Considerations on CHO with CPA/CPC |
Samsung |
| R2-2308303 |
Discussion on CHO including target MCG and candidate SCGs for CPC/CPA |
CMCC |
| R2-2308409 |
CHO with associated SCG |
Interdigital Inc. |
| R2-2308564 |
CHO with associated SCG |
Interdigital Inc. |
| R2-2308750 |
Remaining issues for CHO with candidate SCG |
MediaTek Inc. |
| R2-2308772 |
Discussion on remaining issues of CHO with candidate SCGs |
China Telecom |
| R2-2308786 |
Simultaneous Evaluation for CHO and CPAC |
LG Electronics |
| R2-2308820 |
Discussion on CHO with candidate SCG(s) |
Xiaomi |
| R2-2309266 |
Report of [AT123][027][feMob]CHO with candidate SCGs |
CATT |
| 7.5.1 |
Organizational |
|
| R2-2307014 |
LS on XR capacity enhancements (R1-2306233; contact: Ericsson) |
RAN1 |
| R2-2307064 |
LS reply on TSCAI for XR (S2-2308197; contact: vivo) |
SA2 |
| R2-2307065 |
Reply LS on the N6 PDU Set Identification (S2-2308199; contact: OPPO) |
SA2 |
| R2-2307066 |
LS Reply on Design of RTP Header Extension for PDU Set handling (S2-2308248; contact: Huawei) |
SA2 |
| R2-2307067 |
Non-homogeneous deployment of PDU Set based handling (S2-2308252; contact: Qualcomm) |
SA2 |
| R2-2307076 |
TS 38321 running CR for XR enhancements |
Qualcomm Incorporated |
| R2-2308334 |
Work Plan for Rel-18 WI on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs); Ericsson (RAN1 FL) |
| R2-2308335 |
SA2 Status for XR |
Nokia, Qualcomm (Rapporteurs) |
| R2-2308336 |
SA4 Status for XR |
Nokia, Qualcomm (Rapporteurs) |
| R2-2308337 |
Stage 2 Overview of XR Enhancements |
Nokia, Qualcomm (Rapporteurs) |
| R2-2308352 |
Introduction of XR enhancements into TS 38.331 (running CR) |
Huawei, HiSilicon |
| R2-2308353 |
RRC CR open issues for XR enhancements |
Huawei, HiSilicon |
| R2-2308696 |
Introduction of XR to PDCP |
LG Electronics Inc. |
| R2-2309312 |
Running RLC CR for XR |
vivo |
| R2-2309315 |
Introduction of XR enhancements into TS 38.331 (running CR) |
Huawei, HiSilicon |
| R2-2309316 |
Introduction of XR enhancements to TS 38.321 |
Qualcomm |
| R2-2309318 |
XR Enhancements |
Nokia, Qualcomm (Rapporteurs) |
| R2-2309334 |
Introduction of XR to PDCP |
LG Electronics Inc. |
| 7.5.2 |
XR awareness |
|
| R2-2307164 |
PSER measurement and feedback |
CANON Research Centre France |
| R2-2307295 |
Discussion on XR awareness |
vivo |
| R2-2307346 |
Leftover issues on XR awareness |
CATT |
| R2-2307368 |
Discussion on XR awareness |
Xiaomi Communications |
| R2-2307399 |
Discussions on uplink End of Data Burst indication for XR |
Fujitsu |
| R2-2307472 |
Discussion on remaining issues of XR awareness |
NEC |
| R2-2307531 |
Details of UAI for XR awareness in RAN |
ZTE Corporation, Sanechips |
| R2-2307607 |
Discussion on XR Awareness |
Facebook India |
| R2-2307728 |
Discussion on XR awareness |
Samsung |
| R2-2307828 |
Views on XR-Awareness |
Apple |
| R2-2308023 |
Discussion on PDU sets and data burst awareness in RAN |
Lenovo |
| R2-2308074 |
UE Assistance Information for XR |
Intel Corporation |
| R2-2308127 |
Discussion on XR awareness |
Spreadtrum Communications |
| R2-2308155 |
Considerations on awareness of XR PDU prioritization |
Sony |
| R2-2308183 |
Discussion on XR awareness |
OPPO |
| R2-2308247 |
On XR awareness |
Google Inc. |
| R2-2308330 |
Remaining Issues on XR awareness for UL Traffic |
CMCC |
| R2-2308338 |
Jitter and End of Data Burst |
Nokia, Nokia Shanghai Bell |
| R2-2308350 |
Discussion on XR assistance information for UL |
Huawei, HiSilicon |
| R2-2308401 |
On UE assistance information for XR traffic |
MediaTek Inc. |
| R2-2308518 |
Discussions on UE indicating EoDB to RAN for XR |
Futurewei |
| R2-2308544 |
XR awareness |
InterDigital |
| R2-2308586 |
Discussion on XR awareness |
Ericsson |
| R2-2308610 |
Discussion on XR awareness |
LG Electronics Inc. |
| R2-2308874 |
Discussion on XR awareness |
China Unicom |
| 7.5.3 |
XR-specific power saving |
|
| R2-2307077 |
Power saving enhancements for XR |
Qualcomm Incorporated |
| R2-2307119 |
Discussion on C-DRX enhancements for XR |
Huawei, HiSilicon |
| R2-2307296 |
Analysis on SFN wrap around issue |
vivo |
| R2-2307347 |
Discussion on power saving |
CATT |
| R2-2307369 |
Discussing on XR-specific power saving |
Xiaomi Communications |
| R2-2307533 |
XR-specific power saving |
ZTE Corporation, Sanechips |
| R2-2307704 |
Discussion on various frame rates supported for XR-specific power |
III |
| R2-2307788 |
DRX enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2307807 |
Remaining issues on DRX enhancement for XR |
LG Electronics Inc. |
| R2-2307829 |
Views on Configurations of Rational Number-Based DRX Cycles |
Apple |
| R2-2307891 |
Discussion on DRX enhancement for XR |
ITRI |
| R2-2307901 |
Discussion on C-DRX enhancement for XR |
NEC Corporation |
| R2-2308024 |
Discussion of DRX enhancement |
Lenovo |
| R2-2308184 |
Discussion on XR-specific power saving |
OPPO |
| R2-2308223 |
Discussion on remaining issue of power saving scheme for XR |
Samsung |
| R2-2308278 |
XR-specific power saving enhancement |
Google Inc. |
| R2-2308309 |
Discussion on the DRX enhancement |
CMCC |
| R2-2308402 |
Remaining issues for C-DRX in XR |
MediaTek Inc. |
| R2-2308585 |
Discussion on XR-specific power saving |
Ericsson |
| 7.5.4.1 |
BSR enhancements for XR |
|
| R2-2307078 |
BSR and delay status reporting for XR |
Qualcomm Incorporated |
| R2-2307099 |
Discussion on delay information and BSR enhancement for XR |
Google Inc. |
| R2-2307133 |
Discussion on XR-specific BSR enhancements |
TCL |
| R2-2307156 |
Discussion on BSR enhancements for XR |
Honor |
| R2-2307197 |
Discussion on MAC enhancements for XR-specific capacity improvement |
Huawei, HiSilicon |
| R2-2307243 |
Discussion on delay status reporting for XR |
DENSO CORPORATION |
| R2-2307268 |
Discussions on remaining time reporting |
KDDI Corporation |
| R2-2307297 |
Discussion on BSR enhancements for XR |
vivo |
| R2-2307348 |
Consideration on DSR and BSR |
CATT |
| R2-2307370 |
Discussing on BSR enhancements for XR capacity |
Xiaomi Communications |
| R2-2307400 |
Discussions on delay information reporting |
Fujitsu |
| R2-2307532 |
BSR enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2307609 |
XR BSR and Delay Information Enhancements |
Facebook India |
| R2-2307682 |
Discussion on Delay status reporting |
NTT DOCOMO, INC. |
| R2-2307761 |
Discussions on delay status reporting in BSR for XR |
Futurewei |
| R2-2307762 |
Discussions on new Buffer Status table design for XR |
Futurewei |
| R2-2307789 |
BSR enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2307830 |
Buffer Delay Reporting and BSR Enhancements for XR |
Apple |
| R2-2307902 |
Discussion on delay status reporting for XR |
NEC Corporation |
| R2-2307913 |
New buffer status report table design |
FGI |
| R2-2307914 |
Discussion on BSR enhancements for XR |
III |
| R2-2307942 |
Delay information reporting for XR |
Lenovo |
| R2-2308025 |
Discussion on BSR enhancements |
Lenovo |
| R2-2308076 |
BSR Enhancements for XR |
Intel Corporation |
| R2-2308134 |
Consideration on BSR enhancements for XR |
Spreadtrum Communications |
| R2-2308156 |
Considerations on XR UL PDU set information |
Sony |
| R2-2308157 |
Some considerations on BSR enhancements for XR |
Sony |
| R2-2308185 |
Discussion on BSR enhancement for XR |
OPPO |
| R2-2308310 |
Consideration on BSR enhancement for XR |
CMCC |
| R2-2308372 |
New static BS table and BSR trigger(s) |
NEC |
| R2-2308412 |
Buffer status and remaining time reporting for XR |
Interdigital Inc. |
| R2-2308567 |
Buffer status and remaining time reporting for XR |
Interdigital Inc. |
| R2-2308587 |
Discussion on BSR enhancements for XR |
Ericsson |
| R2-2308677 |
BSR enhancements for XR |
MediaTek Inc. |
| R2-2308875 |
Discussion on new BSR table and delay status report |
LG Electronics Inc. |
| R2-2308883 |
Discussion on BSR enhancements for XR |
Samsung |
| 7.5.4.2 |
Discard operation for XR |
|
| R2-2307079 |
PDU discard operation for XR |
Qualcomm Incorporated |
| R2-2307100 |
Discussion on PDU discard for XR |
Google Inc. |
| R2-2307134 |
Discussion on XR-specific discard enhancements |
TCL |
| R2-2307165 |
Discussion on packet discarding for XR |
CANON Research Centre France |
| R2-2307196 |
Discussion on PDU set discarding for XR traffic |
Huawei, HiSilicon |
| R2-2307298 |
Discussion on discard operation for XR |
vivo |
| R2-2307299 |
Discussion on RLC impacts on PDU set discard |
vivo |
| R2-2307349 |
PDCP discard timer model for PDU Set discard |
CATT, China Unicom, DELL, Ericsson, Intel Corporation, OPPO |
| R2-2307350 |
Discard Operation for XR |
CATT |
| R2-2307371 |
Discussing on PDU discarding of XR traffic |
Xiaomi Communications |
| R2-2307401 |
Discussions on PDU discard based on PDU Set Importance |
Fujitsu |
| R2-2307534 |
PDU discard for XR |
ZTE Corporation, Sanechips |
| R2-2307593 |
Discard Operation for XR |
Samsung R&D Institute India |
| R2-2307608 |
Discussion on PDU Discard Operation for XR |
Facebook India |
| R2-2307763 |
Discussions on PSI-based discard operation for XR |
Futurewei |
| R2-2307831 |
Views on PDU Discard Operation for XR |
Apple |
| R2-2307892 |
Discussion on PSI-based discard operation |
ITRI |
| R2-2307950 |
Remaining details on discarding operation for XR |
Lenovo |
| R2-2307953 |
Remaining details on discarding operation for XR |
Lenovo |
| R2-2308075 |
Discard Enhancements for XR |
Intel Corporation |
| R2-2308128 |
Discussion on XR discard operation |
Spreadtrum Communications |
| R2-2308173 |
Some considerations on PSI and PSIHI |
Sony |
| R2-2308186 |
Discussion on discard operation for XR |
OPPO |
| R2-2308331 |
Further discussions on discard operation for XR |
CMCC |
| R2-2308339 |
Details of PSI-based Discard |
Nokia, Nokia Shanghai Bell |
| R2-2308371 |
PDU discard |
NEC |
| R2-2308546 |
Discard operation for XR |
InterDigital |
| R2-2308588 |
Discussion on PSI-based discarding |
Ericsson |
| R2-2308607 |
Discussion on the discard for XR |
LG Electronics Inc. |
| R2-2308668 |
Further aspects of PDU discard |
MediaTek Inc. |
| R2-2309002 |
Summary of [AT123][201][XR] XR MAC Ces |
Lenovo |
| R2-2309003 |
Report of [AT123][205][XR] Options for PSI-based discard (Ericsson) |
Ericsson |
| 7.5.4.3 |
Configured Grant enhancements for XR |
|
| R2-2307080 |
Configured grant enhancements for XR |
Qualcomm Incorporated |
| R2-2307120 |
Discussin on Multi-PUSCH CG |
Huawei, HiSilicon |
| R2-2307244 |
Discussion on HARQ process ID determination for multi-PUSCHs CG |
DENSO CORPORATION |
| R2-2307245 |
Configured Grant enhancements for XR |
Xiaomi |
| R2-2307351 |
Discussion on configured grant |
CATT |
| R2-2307535 |
Configured Grant enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2307729 |
Discussion on CG enhancements |
Samsung |
| R2-2307790 |
CG enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2307832 |
Views on UTO for Multi-PUSCH Configured Grant |
Apple |
| R2-2307915 |
Discussion on Configured Grant enhancements for XR |
III |
| R2-2307954 |
CG enhancements for XR communications |
Lenovo |
| R2-2308158 |
Configured Grant enhancements for XR |
Sony |
| R2-2308187 |
Discussion on configured grant enhancement for XR |
OPPO |
| R2-2308246 |
On Configured Grant enhancements for XR |
Google Inc. |
| R2-2308311 |
Consideration on CG enhancement for XR |
CMCC |
| R2-2308370 |
CG enhancement for XR |
NEC |
| R2-2308543 |
Configured Grant enhancements for XR |
Ericsson |
| R2-2308547 |
Configured Grant enhancements for XR |
InterDigital |
| R2-2308672 |
HARQ ID determination formula for CG |
MediaTek Inc. |
| R2-2308679 |
Discussion on multiple-PUSCHs CG for XR |
TCL |
| R2-2308876 |
Discussion on CG enhancement for XR |
LG Electronics Inc. |
| R2-2309005 |
[draft] Reply LS on on XR capacity enhancements |
MediaTek Inc. |
| R2-2309006 |
[draft] Reply LS on XR capacity enhancements |
MediaTek Inc. |
| R2-2309007 |
Reply LS on XR capacity enhancements |
RAN2 |
| 7.5.5 |
UE capabilities for XR |
|
| R2-2307081 |
UE capabilities for XR services |
Qualcomm Incorporated |
| R2-2307246 |
UE capabilities for XR |
Xiaomi |
| R2-2307300 |
Discussion on UE capability for XR |
vivo |
| R2-2307536 |
UE capabilities for XR |
ZTE Corporation, Sanechips |
| R2-2307730 |
UE capability for XR |
Samsung |
| R2-2307833 |
Views on UE capabilities for XR |
Apple |
| R2-2308073 |
UE Capabilities for Rel-18 XR WI |
Intel Corporation |
| R2-2308188 |
Discussion on UE capabilities for XR |
OPPO |
| R2-2308340 |
UE capabilities for Rel-18 XR |
Nokia, Nokia Shanghai Bell |
| R2-2308351 |
Discussion on UE capabilities for XR |
Huawei, HiSilicon |
| R2-2308545 |
UE capabilities for XR |
InterDigital |
| R2-2308589 |
Discussion on UE capabilities for XR |
Ericsson |
| 7.6.1 |
Organizational |
|
| R2-2307003 |
LS on GNSS position fix during inactive state of Connected DRX for improved GNSS operations (R1-2304126; contact: MediaTek) |
RAN1 |
| R2-2307005 |
Reply LS on HARQ Enhancements (R1-2306182; contact: OPPO) |
RAN1 |
| R2-2307012 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#113 (R1-2306222; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2307016 |
LS on NPDCCH monitoring restriction for NB-IoT NTN (R1-2306245; contact: Lenovo) |
RAN1 |
| R2-2307625 |
Running CR for TS 36.306 for Rel-18 IoT NTN |
Qualcomm Incorporated |
| R2-2308046 |
36331 running CR for IOT NTN |
Huawei, HiSilicon |
| R2-2308194 |
36.304 Running CR for Rel-18 IoT NTN |
Nokia Solutions & Networks (I) |
| R2-2308542 |
Running CR for IoT NTN |
Ericsson |
| R2-2308904 |
On R18 IoT NTN UE capabilities |
Ericsson |
| R2-2308939 |
Rapporteur input on 36.300 |
Ericsson |
| R2-2308944 |
Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN |
MediaTek Inc. |
| R2-2308990 |
Draft Reply LS on NPDCCH monitoring restriction for NB-IoT NTN |
Lenovo |
| R2-2308993 |
Reply LS on NPDCCH monitoring restriction for NB-IoT NTN |
RAN2 |
| R2-2309286 |
36331 running CR for IOT NTN |
Huawei, HiSilicon |
| R2-2309330 |
36.304 Running CR for Rel-18 IoT NTN |
Nokia |
| R2-2309338 |
Running CR for IoT NTN |
Ericsson |
| R2-2309342 |
Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN |
MediaTek |
| 7.6.2 |
Performance Enhancements |
|
| R2-2308890 |
On improved GNSS operation and HARQ for IoT NTN |
Samsung Electronics Czech |
| 7.6.2.1 |
HARQ enhancements |
|
| R2-2307105 |
Discussion on HARQ Enhancement for IoT NTN |
vivo |
| R2-2307189 |
On Disabling HARQ Feedback in IoT-NTN |
MediaTek Inc. |
| R2-2307250 |
Discussion on HARQ enhancement for IoT NTN |
OPPO |
| R2-2307251 |
Draft reply LS on NPDCCH monitoring restriction for NB-IoT NTN |
OPPO |
| R2-2307413 |
Discussion on HARQ enhancements in IoT NTN |
CATT |
| R2-2307488 |
Discussion on HARQ mode for PUR |
Huawei, Turkcell, HiSilicon |
| R2-2307506 |
Discussion on HARQ enhancement |
Xiaomi |
| R2-2307587 |
Further discussion on HARQ enhancements |
ZTE Corporation, Sanechips |
| R2-2307626 |
HARQ process enhancement |
Qualcomm Incorporated |
| R2-2308228 |
On HARQ enhancements for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2308288 |
Discussion on the HARQ enhancement for IoT-NTN |
CMCC |
| R2-2308541 |
R18 IoT NTN HARQ enhancements |
Ericsson |
| R2-2308576 |
Remaining Issues on Disabling HARQ feedback for IoT-NTN |
Interdigital, Inc. |
| R2-2308981 |
[AT123][101][IoT NTN] HARQ Enhancements (Nokia) |
Nokia, Nokia Shanghai Bell (Rapporteur) |
| 7.6.2.2 |
GNSS operation enhancements |
|
| R2-2307106 |
Discussion on GNSS Operation for IoT NTN |
vivo |
| R2-2307190 |
Enhancements on GNSS operation |
MediaTek Inc. |
| R2-2307259 |
Discussion on GNSS operation for IoT NTN |
OPPO |
| R2-2307414 |
Discussion on GNSS operation in connected mode |
CATT |
| R2-2307477 |
Discussion on the GNSS Validity Reporting |
Google Inc. |
| R2-2307489 |
Discussion on the impact of GNSS measurement |
Huawei, Turkcell, HiSilicon |
| R2-2307505 |
Discussion on GNSS operation enhancement |
Xiaomi |
| R2-2307588 |
Remaining issues of GNSS enhancements |
ZTE Corporation, Sanechips |
| R2-2307629 |
GNSS fix in RRC_CONNECTED |
Qualcomm Incorporated |
| R2-2307865 |
Improved GNSS Operation |
Apple |
| R2-2308008 |
Some remaining issues of GNSS operations for IoT NTN |
Lenovo |
| R2-2308229 |
GNSS operation enhancement in Rel-18 IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2308289 |
Discussion on GNSS enhancement for IoT-NTN |
CMCC |
| R2-2308540 |
R18 IoT NTN GNSS operation enhancements |
Ericsson |
| R2-2308577 |
GNSS acquisition and reporting for IoT NTN |
Interdigital, Inc. |
| R2-2308617 |
Discussion of GNSS operation enhancements |
SHARP Corporation |
| R2-2308881 |
GNSS Validity duration Reporting |
Nordic Semiconductor ASA |
| R2-2308991 |
Report of [AT123][110][IoT NTN Enh] GNSS enhancements |
ZTE (rapporteur) |
| 7.6.3 |
Mobility Enhancements |
|
| R2-2307192 |
Report of [Post122][112][IoT NTN Enh] Mobility |
MediaTek Inc. |
| R2-2307589 |
Remaining issues of mobility enhancements |
ZTE Corporation, Sanechips |
| 7.6.3.1 |
Enhancements for neighbour cell measurements |
|
| R2-2307191 |
Remaining Enhancements on Neighbor Cell Measurements in IoT-NTN |
MediaTek Inc. |
| R2-2307252 |
Discussion on mobility enhancement for IoT NTN |
OPPO |
| R2-2307511 |
Discussion on UE behavior when serving cell t-service expires |
Xiaomi |
| R2-2307628 |
Measurement and Mobility enhancements |
Qualcomm Incorporated |
| R2-2307772 |
On remaining issues of IoT-NTN mobility enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2307866 |
Neighbour cell measurements before RLF for NB-IoT |
Apple |
| R2-2308034 |
Enhancements for neighbour cell measurements |
Huawei, Turkcell, HiSilicon |
| R2-2308578 |
Open issues on mobility enhancements (not covered by [Post122][112]) |
Interdigital, Inc. |
| R2-2308811 |
Discussion on gaps for neighbour cell measurements in IoT NTN |
Ericsson |
| R2-2308891 |
On enhancements for neighbour cell measurements |
Samsung Electronics Czech |
| 7.6.3.2 |
Other |
|
| R2-2307107 |
Discussion on Mobility Enhancement for R18 IoT NTN |
vivo |
| R2-2307867 |
Mobility enhancement in IoT NTN |
Apple |
| R2-2308035 |
Discussion on CHO enhancements |
Huawei, Turkcell, HiSilicon |
| R2-2308290 |
Discussion on CHO enhancements for eMTC NTN |
CMCC |
| R2-2308892 |
On CHO and other mobility enhancements for IoT NTN |
Samsung Electronics Czech |
| 7.6.4 |
Enhancements to discontinuous coverage |
|
| R2-2307108 |
Discussion on Discontinuous Coverage for R18 IoT NTN |
vivo |
| R2-2307319 |
Discontinuous coverage handling enhancement for IoT NTN |
THALES, Telit |
| R2-2307415 |
Discussion on enhancements to discontinuous coverage |
CATT |
| R2-2307444 |
Considerations on Supporting Discontinuous Coverage |
NEC |
| R2-2307497 |
Report of [Post122][113][IoT NTN Enh] Discontinuous coverage (Huawei) |
Huawei, HiSilicon |
| R2-2307590 |
Remaining issues of discontinuous coverage |
ZTE Corporation, Sanechips |
| R2-2307627 |
RRC release procedure in discontinuous coverage |
Qualcomm Incorporated |
| R2-2307773 |
Further discussion on discontinuous coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2307868 |
Support on discontinuous coverage in IoT NTN |
Apple |
| R2-2308009 |
Some remaining issues for discontinuous coverage |
Lenovo |
| R2-2308217 |
Discussion on enhancement to discontinuous coverage for IoT NTN |
Transsion Holdings |
| R2-2308285 |
Enhancements to discontinuous coverage |
Samsung R&D Institute UK |
| R2-2308579 |
Paging in discontinuous coverage |
Interdigital, Inc. |
| R2-2308580 |
LS on PTW modification due to UE unreachability |
Interdigital, Inc. |
| R2-2308717 |
Discussion on TN coverage for discontinuous coverage |
ASUSTeK |
| R2-2309283 |
LS on misalignment between PTW and Coverage Window |
RAN2 |
| 7.7.1 |
Organizational |
|
| R2-2307008 |
Reply LS to RAN2 on unchanged PCI (R1-2306210; contact: CATT) |
RAN1 |
| R2-2307011 |
Reply LS on RACH-less Handover (R1-2306217; contact: Samsung) |
RAN1 |
| R2-2307035 |
LS on time-based trigger condition in NG HO for NR NTN (R3-233527; contact: Ericsson) |
RAN3 |
| R2-2307318 |
Stage 2 running CR for TS 38.300 for Rel-18 NTN enhancements |
THALES (Rapporteur) |
| R2-2307323 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R2-2308092 |
UE Capability Discussion for Rel-18 NR NTN Enhancements WI |
Intel Corporation |
| R2-2308093 |
UE capabilities for Rel-18 NR NTN Enhancements WI |
Intel Corporation |
| R2-2308094 |
UE capabilities for Rel-18 NR NTN Enhancements WI |
Intel Corporation |
| R2-2308523 |
Stage 3 NTN running CR for 38.321 - RAN2#122 |
InterDigital |
| R2-2308902 |
Stage 3 Running RRC CR for NR NTN Rel-18 |
Ericsson |
| R2-2308937 |
Stage 3 Running RRC CR for NR NTN Rel-18 |
Nanjing Ericsson Panda Com Ltd |
| R2-2308943 |
Running 38.304 CR for NTN |
ZTE Corporation, Sanechips |
| R2-2309327 |
Stage 3 running 38.304 CR for NTN |
ZTE Corporation, Sanechips |
| R2-2309329 |
Stage-2 running CR for TS 38.300 for Rel-18 NTN enhancements |
THALES (Rapporteur) |
| R2-2309341 |
Stage 3 Running RRC CR for NR NTN Rel-18 |
Ericsson |
| R2-2309345 |
Stage-3 running CR for TS 38.321 for Rel-18 NTN |
InterDigital |
| 7.7.2 |
Coverage Enhancements |
|
| R2-2307195 |
Discussion on PUCCH repetition for Msg4 HARQ-ACK for NTN |
NTT DOCOMO INC. |
| R2-2307253 |
Discussion on PUCCH enhancement for Msg4 HARQ-ACK in NR NTN |
OPPO |
| R2-2307313 |
Discussion on signalling for PUCCH repetition for Msg4 HARQ-ACK |
Samsung |
| R2-2307416 |
Discussion on PUCCH repetition for Msg4 HARQ-ACK |
CATT |
| R2-2307512 |
Discussion on coverage enhancement for NR NTN |
Xiaomi |
| R2-2307526 |
Higher layer signalling for PUCCH repetition for Msg4 HARQ-ACK |
Huawei, HiSilicon |
| R2-2307620 |
UE capability indication for Msg4 ACK repetition |
Qualcomm Incorporated |
| R2-2307839 |
HL signaling design for the PUCCH repetition request |
Apple |
| R2-2308230 |
On Msg3 indication for PUCCH repetition for Msg4 HARQ-ACK |
Nokia, Nokia Shanghai Bell |
| R2-2308294 |
Discussion on the LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK |
CMCC |
| R2-2308507 |
Consideration on coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2308539 |
R18 NR NTN Coverage enhancements |
Ericsson |
| R2-2308604 |
Discussion on coverage enhancement |
LG Electronics Inc. |
| R2-2308988 |
Outcome of [AT123][108][NR NTN Enh] LCID extension (Huawei) |
Huawei, HiSilicon |
| 7.7.3 |
Network verified UE location |
|
| R2-2307320 |
Discussion on network verified UE location in NR NTN |
THALES |
| R2-2307487 |
Discussion on the network verfied UE location |
Huawei, Turkcell, HiSilicon |
| R2-2307601 |
UE support of Network Verified UE Location Feature |
Samsung R&D Institute UK |
| R2-2307908 |
Discussion on network verified UE location |
Ericsson |
| R2-2308196 |
Discussion on multiple-RTT based positioning in NTN |
Quectel |
| R2-2308263 |
Discussion on network verified UE location |
Xiaomi |
| R2-2308277 |
Discussion on NTN NW verified UE location |
Lenovo |
| R2-2308295 |
Considerations on network verified UE location |
CMCC |
| R2-2308450 |
UE location verification by Network |
NEC Telecom MODUS Ltd. |
| R2-2308706 |
Discussion on Network Verified UE Location |
TCL |
| R2-2308777 |
On Network verified UE location for NR NTN |
MediaTek Inc. |
| 7.7.4.1 |
Cell reselection enhancements |
|
| R2-2307314 |
Discussion on Cell Reselection Enhancements |
Samsung |
| R2-2307321 |
Discussion on mobility enhancements for VSAT |
THALES |
| 7.7.4.1.1 |
NTN-TN enhancements |
|
| R2-2307101 |
Remaining Issues on Power Saving for NTN-TN Mobility |
vivo |
| R2-2307166 |
NTN neighbour cell information in TN cells |
PANASONIC R&D Center Germany |
| R2-2307167 |
Considerations on TN-NTN cell re-selection |
Telit Communications S.p.A. |
| R2-2307217 |
Discussion on providing TN coverage area information |
LG Electronics France |
| R2-2307254 |
Discussion on NTN-TN cell reselection enhancement |
OPPO |
| R2-2307417 |
Discussion on the mechanism for providing TN coverage information |
CATT |
| R2-2307579 |
On TN Coverage Definition and TN to NTN Reselections |
Nokia, Nokia Shanghai Bell |
| R2-2307621 |
TN cell coverage info and measurement relaxation |
Qualcomm Incorporated |
| R2-2307739 |
Discussion on NTN to TN cell reselection enhancements |
TCL |
| R2-2307840 |
NTN-TN cell reselection enhancement |
Apple |
| R2-2308010 |
Some remaining issues for TN area information |
Lenovo |
| R2-2308054 |
Discussion on the NTN – TN cell reselection enhancement |
Turkcell, Huawei, HiSilicon |
| R2-2308116 |
Discussion on NTN-TN enhancements |
NTT DOCOMO, INC. |
| R2-2308218 |
Discussion on remaining issues of NTN-TN cell reselection enhancements |
Transsion Holdings |
| R2-2308239 |
Discussion on TN coverage description |
ETRI |
| R2-2308264 |
Cell reselection enhancements for NTN-TN mobility |
Xiaomi |
| R2-2308283 |
Signaling of the TN coverage area and the frequency information |
ZTE corporation, Sanechips |
| R2-2308296 |
Discussion on open issues for NTN-TN cell reselection |
CMCC |
| R2-2308524 |
NTN-TN mobility and service continuity |
InterDigital |
| R2-2308701 |
Discussion on NTN-TN Cell re-selection |
ITL |
| 7.7.4.1.2 |
NTN-NTN enhancements |
|
| R2-2307102 |
Further discussion NTN-NTN Mobility for Earth-moving Cell |
vivo |
| R2-2307218 |
Discussion on NTN-NTN cell reselection enhancements |
LG Electronics France |
| R2-2307255 |
Discussion on NTN-NTN cell reselection enhancement |
OPPO |
| R2-2307740 |
Discussion on NTN to NTN cell reselection enhancements |
TCL |
| R2-2308011 |
Feeder link switch time and reference location of NTN moving cells |
Lenovo |
| R2-2308033 |
Discussion on location-based measurement initiation in moving cells |
Huawei, Turkcell, HiSilicon |
| R2-2308124 |
Discussion on NTN-NTN mobility enhancements |
Spreadtrum Communications |
| R2-2308265 |
Cell reselection enhancements for NTN-NTN mobility |
Xiaomi |
| R2-2308297 |
Discussion on remaining issues for NTN-NTN reselection |
CMCC |
| R2-2308525 |
Cell reselection enhancements for Earth moving cell |
InterDigital |
| R2-2308700 |
Discussion on NTN-NTN cell reselection enhancements |
CAICT |
| R2-2308718 |
Discussion on description of movingReferenceLocation |
ASUSTeK |
| R2-2308901 |
Idle mode mobility enhancements |
Ericsson |
| 7.7.4.2 |
Handover enhancements |
|
| R2-2307103 |
Discussion on Handover Enhancement with Common HO Configuration in NR NTN |
vivo |
| R2-2307104 |
Further Discusison on Service Link Switch with Unchanged PCI |
vivo |
| R2-2307193 |
On Triggering Unchanged PCI for Handover Enhancement in LEO NTN |
MediaTek Inc. |
| R2-2307219 |
Discussion on handover enhancements |
LG Electronics France |
| R2-2307258 |
Discussion on NTN handover enhancements |
OPPO |
| R2-2307315 |
Discussion on Handover Enhancements |
Samsung |
| R2-2307343 |
Handover enhancements |
Continental Automotive |
| R2-2307418 |
Discussion on unchanged PCI scenario |
CATT |
| R2-2307419 |
Discussion on RACH-less and common (C)HO configuration |
CATT |
| R2-2307476 |
Discussion on the Unchanged PCI Satellite Switch |
Google Inc. |
| R2-2307580 |
Resolving Open Points on RACH-less HO in Rel-18 NTN |
Nokia, Nokia Shanghai Bell |
| R2-2307581 |
On Unchanged PCI and Satellite Switching without L3 Mobility |
Nokia, Nokia Shanghai Bell |
| R2-2307622 |
RACH-less handover for NTN |
Qualcomm Incorporated |
| R2-2307623 |
Details on satellite switch with PCI unchange |
Qualcomm Incorporated |
| R2-2307741 |
Discussion on satellite switch with unchanged PCI |
Panasonic |
| R2-2307841 |
Hard satellite switching with unchanged PCI |
Apple |
| R2-2307842 |
NR NTN specific HO enhancement |
Apple |
| R2-2307893 |
Discussion on gap time of unchanged PCI |
ITRI |
| R2-2307894 |
Discussion on common information of group handover |
ITRI |
| R2-2307896 |
Discussion on soft satellite switching with PCI unchanged |
FGI |
| R2-2307943 |
RACH-less signaling design for NTN |
China Telecom |
| R2-2308012 |
Some remaining issues for RACH-less HO in NTN |
Lenovo |
| R2-2308032 |
Remaining issues on RACH-less HO in NTN |
Huawei, Turkcell, HiSilicon |
| R2-2308146 |
Discussion on RACH-less HO |
Sharp |
| R2-2308159 |
Signaling overhead reduction during NTN-NTN HOs |
Sony |
| R2-2308219 |
Discussion on open issues of NTN-NTN handover |
Transsion Holdings |
| R2-2308266 |
Discussion on handover enhancements for NTN-NTN mobility |
Xiaomi |
| R2-2308329 |
Report of [Post122][114][NR NTN Enh] Unchanged PCI |
CMCC |
| R2-2308373 |
Satellite Switch, PCI change without L3 handover |
NEC |
| R2-2308374 |
Support RACH-less CHO |
NEC |
| R2-2308526 |
NTN mobility enhancements for RRC_CONNECTED |
InterDigital |
| R2-2308527 |
Satellite switching without PCI change |
InterDigital |
| R2-2308609 |
Discussion on NTN handover enhancements |
Fujitsu |
| R2-2308719 |
Discussion on moving cell reference location for CHO |
ASUSTeK |
| R2-2308752 |
Discussion on random access in the unchanged PCI scenario |
ETRI |
| R2-2308753 |
“Unchanged PCI” solution vs “PCI change only” solution |
Sequans Communications |
| R2-2308755 |
Common signalling of HO common information |
Sequans Communications |
| R2-2308900 |
Handover enhancements |
Ericsson |
| R2-2308989 |
Report of [AT123][109][NR NTN Enh] RACH-less HO (Samsung) |
Samsung |
| 7.8.1 |
Organizational |
|
| R2-2307034 |
Reply LS to RAN2 on flightpath information forwarding for UAV (R3-233493; contact: ZTE) |
RAN3 |
| R2-2307059 |
Reply LS on BRID and DAA broadcast over LTE and NR PC5 (S2-2307781; contact: LGE) |
SA2 |
| R2-2307582 |
Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan |
Nokia, Nokia Shanghai Bell |
| R2-2307583 |
38.300 Running CR for Rel-18 UAVs |
Nokia, Nokia Shanghai Bell |
| R2-2307634 |
RRC Running CR (Introduction of Aerial Support) |
Qualcomm Incorporated |
| R2-2309344 |
Introduction of UAV support in Rel-18 NR |
Nokia, Nokia Shanghai Bell |
| 7.8.2 |
Measurement reporting for mobility and interference control |
|
| R2-2307441 |
Discussion on Measurement Reports Enhancements |
NEC |
| R2-2307463 |
UAV measurement reports |
Ericsson |
| R2-2307635 |
Measurement and reporting enhancements |
Qualcomm Incorporated |
| R2-2307681 |
Further discussion on NR support for UAV |
NTT DOCOMO, INC. |
| R2-2307734 |
On height-dependent SSB-ToMeasure configuration |
ZTE Corporation, Sanechips |
| R2-2307735 |
On measurement reporting enhancement |
ZTE Corporation, Sanechips |
| R2-2307869 |
Measurement reporting enhancement in UAV |
Apple |
| R2-2307996 |
Discussion on height dependent measurement for NR UAV |
Lenovo |
| R2-2308298 |
Discussion on the FFS issues for measurement reporting |
CMCC |
| R2-2308605 |
On Height-dependent Measurement Report Configuration for UAVs |
Nokia, Nokia Shanghai Bell |
| R2-2308651 |
Discussion on Measurement Reporting for NR UAV |
China Telecom |
| R2-2308686 |
Discussion on no-transmit-zone |
LG Electronics |
| R2-2308702 |
Measurement report enhancement for NR UAV |
Huawei, HiSilicon |
| R2-2308707 |
Remaining issues on measurement reporting enhancements in NR UAV |
Samsung Electronics Nordic AB |
| R2-2308797 |
Measurement Report Enhancement |
LG Electronics |
| R2-2308821 |
Discussion on measurement reporting enhancements for NR UAV |
Xiaomi |
| R2-2308832 |
Discussion on measurement reporting enhancement for NR UAV |
vivo |
| R2-2308833 |
Discussion on combination event for NR UAV |
vivo |
| 7.8.3 |
Flight path reporting |
|
| R2-2307279 |
Consideration on flight path reporting for NR UAV |
DENSO CORPORATION |
| R2-2307442 |
Discussion on Flight Path Reporting |
NEC |
| R2-2307584 |
Even Further Details on Flight Path Plan (FPP) |
Nokia, Nokia Shanghai Bell |
| R2-2307636 |
Flight path reporting enhancements |
Qualcomm Incorporated |
| R2-2307736 |
On flight path reporting |
ZTE Corporation, Sanechips |
| R2-2307870 |
Flight path reporting in UAV |
Apple |
| R2-2307918 |
Discussion on flight path reporting for NR UAV |
Sharp |
| R2-2307997 |
Remaining issues of flight path reporting for NR UAV |
Lenovo |
| R2-2308299 |
Considerations on the remaining issues for flight path reporting |
CMCC |
| R2-2308467 |
UAV Flight Path Reporting |
Ericsson España S.A. |
| R2-2308528 |
Flightpath update notification for UAV |
InterDigital |
| R2-2308529 |
Flightpath reporting for UAV |
InterDigital |
| R2-2308653 |
Discussion on Flight Path Reporting for NR UAV |
China Telecom |
| R2-2308692 |
Discussion on flight path reporting |
Samsung |
| R2-2308704 |
Further discussion on flight path reporting |
Huawei, HiSilicon |
| R2-2308720 |
Discussion on triggering of flight path report |
ASUSTeK |
| R2-2308798 |
Flight Path Information Report |
LG Electronics |
| R2-2308822 |
Discussion on flight path reporting for NR UAV |
Xiaomi |
| R2-2308834 |
Discussion on flight path reporting |
vivo |
| 7.8.5 |
UAV identification broadcast |
|
| R2-2307443 |
Considerations on Enhancements for UAV identification broadcast |
NEC |
| R2-2307585 |
On the Remaining Aspects for Supporting PC5-based BRID and DAA |
Nokia, Nokia Shanghai Bell |
| R2-2307637 |
Remaining aspects of PC5-based BRID and DAA support |
Qualcomm Incorporated |
| R2-2307731 |
SL configuration for UAV ID/DAA broadcast |
Samsung |
| R2-2307871 |
BRID and DAA support over PC-5 |
Apple |
| R2-2307998 |
Discussion on broadcasting remote id for UAV |
Lenovo |
| R2-2308300 |
Discussion on UAV identification broadcast |
CMCC |
| R2-2308468 |
UAV Broadcast Identification |
Ericsson España S.A. |
| R2-2308560 |
Resources for broadcast of BRID and DAA |
Beijing Xiaomi Mobile Software |
| R2-2308705 |
Further discussion on UAV remote identification broadcast |
Huawei, HiSilicon |
| 7.9.1 |
Organizational |
|
| R2-2307055 |
Reply LS on 5G ProSe Layer-2 UE-to-UE Relay QoS enforcement (S2-2305915; contact: Qualcomm) |
SA2 |
| R2-2307057 |
Reply LS to SA2 on authorization for multi-path Scenario 2 (S2-2307707; contact: LGE) |
SA2 |
| R2-2307072 |
Reply LS on security for L2 UE-to-UE relay (S3-233323; contact: Lenovo) |
SA3 |
| R2-2307235 |
Running CR of TS 38.351 for SL Relay enhancement |
OPPO |
| R2-2307546 |
Introduction of NR sidelink U2U relay |
vivo |
| R2-2307720 |
38.322 running CR for enhanced NR sidelink relay |
Xiaomi |
| R2-2307854 |
Draft Running CR 38.321 |
Apple |
| R2-2307920 |
Draft running CR 38.300 |
LG Electronics Inc. |
| R2-2308203 |
RRC running CR for Rel-18 multi-path support |
Huawei, HiSilicon |
| R2-2308204 |
Considerations on Multi-path RRC running CR |
Huawei, HiSilicon |
| R2-2308559 |
Introduction of Rel-18 support for SL Relay Enhancements |
Ericsson España S.A. |
| R2-2308687 |
Introduction of Rel-18 SL relay service continuity |
MediaTek, Inc |
| R2-2309184 |
Running CR of TS 38.351 for SL Relay enhancement |
OPPO |
| R2-2309185 |
Introduction of NR sidelink U2U relay |
vivo |
| R2-2309186 |
38.322 running CR for enhanced NR sidelink relay |
Xiaomi |
| R2-2309187 |
Draft Running CR 38.321 |
Apple |
| R2-2309188 |
Draft running CR 38.300 |
LG Electronics Inc. |
| R2-2309189 |
RRC running CR for Rel-18 multi-path support |
Huawei, HiSilicon |
| R2-2309225 |
Introduction of Rel-18 support for SL Relay Enhancements |
Ericsson España S.A. |
| R2-2309226 |
Introduction of Rel-18 SL relay service continuity |
MediaTek, Inc |
| R2-2309308 |
Introduction of NR sidelink U2U relay |
vivo |
| R2-2309309 |
Draft_stage2 running CR (38.300) for Rel-18 relay enhancement |
LG Electronics |
| R2-2309310 |
RRC running CR for Rel-18 multi-path |
Huawei, HiSilicon |
| R2-2309333 |
Running CR of TS 38.351 for NR sidelink relay enhancements |
OPPO |
| R2-2309339 |
Draft_stage2 running CR (38.300) for Rel-18 relay enhancement |
LG Electronics |
| 7.9.2 |
UE-to-UE relay |
|
| R2-2307233 |
Discussion on U2U relay |
OPPO |
| R2-2307386 |
Discussion on remaining issue of U2U relay |
NEC |
| R2-2307402 |
Discussion on the adaptation layer |
Fujitsu |
| R2-2307446 |
Discussion on U2U relay |
Sharp |
| R2-2307547 |
Remaining issues on U2U discovery and relay (re)selection |
vivo |
| R2-2307548 |
Discussion on the remaining issues of L2 U2U relaying |
vivo |
| R2-2307551 |
Discussion on U2U Relay |
CATT |
| R2-2307641 |
U2U Relay selection reselection, SRAP design |
Beijing Xiaomi Mobile Software |
| R2-2307655 |
Discussion on using short ID in U2U relaying |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2307716 |
Discussion on U2U relay |
TCL |
| R2-2307732 |
QoS and bearer configuration for L2 U2U relaying |
Samsung |
| R2-2307742 |
Common part and Layer-2 specific part on U2U Relay |
Qualcomm Incorporated |
| R2-2307743 |
gNB involvement and capability on U2U relay |
Qualcomm Incorporated |
| R2-2307750 |
Considerations for U2U L2 relay operations |
Kyocera |
| R2-2307855 |
Discussion on remaining issues on UE-to-UE Relay |
Apple |
| R2-2307932 |
Control plane procedure for U2U relay |
LG Electronics Inc. |
| R2-2307944 |
Further discussion on L2 U2U relay |
China Telecom |
| R2-2307989 |
Discussion on L2 U2U relay |
Lenovo |
| R2-2308100 |
Discussion on U2U Relay discovery and (re)selection |
ZTE, Sanechips |
| R2-2308101 |
Discussion on U2U relay L2-specific functionality |
ZTE, Sanechips |
| R2-2308104 |
SRAP design for U2U Sidelink Relay |
Samsung |
| R2-2308119 |
Discussion on UE-to-UE Relay |
Spreadtrum Communications |
| R2-2308160 |
UE-to-UE relay (re)selection |
Sony |
| R2-2308161 |
Discussion on DRX for Sidelink UE to UE Relay |
Sony |
| R2-2308205 |
Discussion on UE-to-UE relay |
Huawei, HiSilicon |
| R2-2308220 |
Remaining issues for UE-to-UE relay |
Sharp |
| R2-2308321 |
Discussion on U2U relay |
CMCC |
| R2-2308368 |
Considerations on U2U relay (re)selection and Local ID assignment |
Nokia, Nokia Shanghai Bell |
| R2-2308380 |
Open Issues on Discovery, Relay Selection, and SRAP for UE to UE Relays |
InterDigital |
| R2-2308381 |
QoS and Configuration for L2 UE-to-UE Relays |
InterDigital |
| R2-2308469 |
Discussion on Relay (re)selection and Discovery |
Ericsson España S.A. |
| R2-2308470 |
Control Plane Procedures for Layer 2 UE-to-UE Relays |
Ericsson España S.A. |
| R2-2308611 |
Discussion on Adaptation Layer for L2 U2U Relay |
ETRI |
| R2-2308721 |
Discussion on E2E PC5-RRC procedures |
ASUSTeK |
| R2-2308722 |
Discussion on AS layer configuration for L2 U2U Relay |
ASUSTeK |
| R2-2308952 |
Discussion on U2U relay |
Sharp |
| R2-2308956 |
[Pre123][404][Relay] Summary of AI 7.9.2 on UE-to-UE relay (Qualcomm) |
Qualcomm |
| R2-2309101 |
Summary proposals on UE-to-UE relay |
Qualcomm Incorporated (Moderator) |
| R2-2309178 |
[DRAFT] LS on U2U Agreements |
InterDigital |
| R2-2309231 |
LS on U2U Agreements |
RAN2 |
| R2-2309270 |
LS on U2U Agreements |
RAN2 |
| 7.9.3 |
Service continuity enhancements for L2 UE-to-network relay |
|
| R2-2307226 |
Discussion on service continuity enhancement |
Xiaomi |
| R2-2307281 |
SL Relay service continuity considerations |
Nokia, Nokia Shanghai Bell |
| R2-2307549 |
Remaining issues on service continuity enhancement for L2 U2N relay |
vivo |
| R2-2307552 |
Further Consideration on Service Continuity Enhancements |
CATT |
| R2-2307733 |
Discussion on measurement quantity configuration |
Samsung |
| R2-2307744 |
Proposal on additional enhancements for service continuity |
Qualcomm Incorporated |
| R2-2307856 |
Discussion on path switching to IDLE/INACTIVE relay |
Apple |
| R2-2307940 |
Discussion on Remaining Issues of Service Continuity |
NEC Corporation |
| R2-2307945 |
Discussion on the procedure for intra-gNB indirect to indirect path switch |
China Telecom |
| R2-2307990 |
Discussion on enhanced path switching |
Lenovo |
| R2-2308102 |
Further discussion on service continuity for SL relay |
ZTE, Sanechips |
| R2-2308162 |
Service continuity enhancements for UE sidelink relay |
Sony |
| R2-2308221 |
Remaining issues for U2N path switching |
Sharp |
| R2-2308322 |
Discussion on service continuity |
CMCC |
| R2-2308471 |
Discussion on Inter-gNB Service Continuity |
Ericsson España S.A. |
| R2-2308584 |
Discussion on Service Continuity |
Huawei, HiSilicon |
| 7.9.4 |
Multi-path relaying |
|
| R2-2307093 |
Discussion on multi-path SL relay |
OPPO |
| R2-2307182 |
Discussion on Multi-path relaying |
Lenovo |
| R2-2307227 |
Discussion on multi-path |
Xiaomi |
| R2-2307363 |
Discussion on non-split SRB |
OPPO, Samsung, China Telecom, Huawei, HiSilicon, Ericsson, vivo, CMCC |
| R2-2307387 |
Discussion on remaining issue of multi-path relay |
NEC |
| R2-2307403 |
Discussions on multi-path |
Fujitsu |
| R2-2307550 |
Remaining Issues for Multi-path Scenario 1 2 |
vivo |
| R2-2307553 |
Discussion on Multi-path |
CATT |
| R2-2307656 |
Throughput Enhancement in U2N Relaying |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2307719 |
Discussion on multi-path scenario 1 |
III |
| R2-2307745 |
Open issues on multi-path relay for scenario 1 and scenario 2 |
Qualcomm Incorporated |
| R2-2307751 |
Considerations for multipath relay operations for Scenario 1 |
Kyocera |
| R2-2307857 |
Discussion on Multi-path Relay |
Apple |
| R2-2307941 |
Discussion on UP Issues of Multi-path relay |
NEC Corporation |
| R2-2307946 |
Discussion on remaining issues of multi-path relaying in Scenario 1 |
China Telecom |
| R2-2307947 |
Discussion on remaining issues of multi-path relaying in Scenario 2 |
China Telecom |
| R2-2307973 |
Report of [AT121bis-e][419][Relay] Remaining high-priority proposals on multi-path (LG) |
LG Electronics France |
| R2-2307991 |
Procedure for second path addition |
Lenovo |
| R2-2308103 |
Further discussion on the support of multi-path relaying |
ZTE, Sanechips |
| R2-2308120 |
Discussion on multi-path relaying |
Spreadtrum Communications |
| R2-2308163 |
Multi-path relaying discussion |
Sony |
| R2-2308206 |
Remaining issues on multi-path operation |
Huawei, HiSilicon |
| R2-2308222 |
Remaining issues for multi-path relay |
Sharp |
| R2-2308224 |
Discussion on remaining issues on multiple path for sidelink relay |
Samsung |
| R2-2308323 |
Discussion on multi-path scenario 1 |
CMCC |
| R2-2308324 |
Considerations on multi-path scenario 2 |
CMCC |
| R2-2308382 |
User Plane Aspects for Multipath |
InterDigital |
| R2-2308383 |
Control Plane Aspects for Multipath |
InterDigital |
| R2-2308472 |
Discussion on Multipath Relays |
Ericsson España S.A. |
| R2-2308723 |
BSR reporting for Multi-path Scenario 2 |
ASUSTeK |
| R2-2308724 |
Discussion on duplicate PDCP PDU discarding for Multi-path transmission Scenario 1 |
ASUSTeK |
| R2-2308749 |
On Remaining issues on multipath SL relay |
Nokia, Nokia Shanghai Bell |
| R2-2308949 |
Summary of A.I 7.9.4 |
Nokia, Nokia Shanghai Bell |
| R2-2308950 |
Report of [Post122][403][Relay] Procedures for multi-path relay (LG) |
LG Electronics Inc. |
| R2-2309174 |
[AT123][432][Relay] Spec impact of case G in scenario 2 |
Xiaomi |
| R2-2309204 |
Summary of [AT123][432][Relay] Spec impact of case G in scenario 2 (Xiaomi) |
Xiaomi |
| 7.9.5 |
DRX |
|
| R2-2307228 |
Discussion on SL DRX in U2N relay |
Xiaomi |
| R2-2307234 |
Discussion on DRX for L2 U2N relay |
OPPO |
| R2-2307554 |
Discussion on DRX for L2 U2N Relay |
CATT |
| R2-2307858 |
Discussion on SL DRX for L2 UE-to-NW relay |
Apple |
| R2-2308207 |
Discussion on sidelink DRX for L2 U2N relay |
Huawei, HiSilicon |
| R2-2308369 |
Considerations on DRX and paging for sidelink relay |
Nokia, Nokia Shanghai Bell |
| 7.10 |
IDC enhancements for NR and MR-DC |
|
| R2-2307544 |
Further Considertion on the IDC reporting |
ZTE Corporation, Sanechips |
| R2-2307651 |
IDC Enhancements |
Qualcomm Incorporated |
| R2-2307767 |
UE interface for IDC |
Nokia, Nokia Shanghai Bell |
| R2-2307909 |
draft _Correction to 38.300 running CR on IDC |
Ericsson |
| R2-2307919 |
Corrections on IDC assistant information |
Sharp |
| R2-2308225 |
Discussion on IDC problem over sidelink |
Samsung, Ericsson |
| R2-2308583 |
Corrections for 38.331 Running CR for IDC Enhancements |
Huawei, HiSilicon |
| R2-2308676 |
TS 38.331 Clarification on the candidateBandwidth field |
vivo |
| R2-2309041 |
Summary of [AT123][651][IDC] Corrections on TS 38.331 Agreed in principle CR (Xiaomi) |
Xiaomi |
| R2-2309042 |
38.331 running CR for introduction of IDC |
Xiaomi |
| R2-2309043 |
Introduction of In-Device Co-existence (IDC) enhancements for NR |
Huawei, HiSilicon |
| R2-2309044 |
38.331 running CR for introduction of IDC |
Xiaomi |
| 7.11.1 |
Organizational |
|
| R2-2307015 |
Reply LS on multicast reception in RRC_INACTIVE (R1-2306243; contact: Apple) |
RAN1 |
| R2-2307112 |
Initial Consideration on UE Capability of eMBS |
vivo |
| R2-2307492 |
RRC running CR for eMBS |
Huawei, HiSilicon |
| R2-2308957 |
MAC running CR for eMBS |
Apple |
| R2-2309033 |
RRC running CR for eMBS |
Huawei, HiSilicon |
| R2-2309034 |
38.300 Running CR for MBS enhancements |
CMCC |
| R2-2309035 |
PDCP Running CR for eMBS |
Xiaomi |
| R2-2309036 |
MAC running CR for eMBS |
Apple |
| 7.11.2.1 |
Control plane |
|
| R2-2307084 |
Control plane for multicast reception in RRC_INACTIVE state |
TD Tech, Chengdu TD Tech |
| R2-2307085 |
MCCH change notification for multicast sessions in RRC_INACTIVE state |
TD Tech, Chengdu TD Tech |
| R2-2307109 |
Discussion on eMBS from the CP Perspective |
vivo |
| R2-2307135 |
Control plane discussion for multicast reception in RRC INACTIVE |
MediaTek inc. |
| R2-2307155 |
Discussion on security issue with multicast MCCH |
CANON Research Centre France |
| R2-2307263 |
Discussion on Control Plane for Multicast Reception in RRC_INACTIVE |
CATT, CBN |
| R2-2307412 |
Consideration on the control plane issue for multicast reception in RRC_INACTIVE |
Beijing Xiaomi Software Tech |
| R2-2307459 |
Discussion on control plane for Multicast reception in RRC_INACTIVE |
NEC Corporation |
| R2-2307493 |
CP issues for multicast reception for RRC INACTIVE UE |
Huawei, HiSilicon |
| R2-2307594 |
CP aspects for Multicast reception in RRC_INACTIVE |
Samsung R&D Institute India |
| R2-2307638 |
Service continuity, RRC state transitions and notifications |
Qualcomm Incorporated |
| R2-2307768 |
Control plane details for multicast reception in RRC_INACTIVE state |
Nokia, Nokia Shanghai Bell |
| R2-2307779 |
RRC Resume for Multicast in RRC_INACTIVE |
SHARP Corporation |
| R2-2307843 |
Control plane aspects for multicast reception in RRC INACTIVE |
Apple |
| R2-2307895 |
Discussion on SDT and MBS multicast reception in RRC_INACTIVE |
ITRI |
| R2-2308013 |
Control plane aspects of Multicast reception in RRC_INACTIVE |
Lenovo |
| R2-2308109 |
Control plane aspects on multicast reception in RRC INACTIVE |
Kyocera |
| R2-2308133 |
Discussion on Service Continuity and RRC state transitions |
Spreadtrum Communications |
| R2-2308200 |
PTM configuration and session deactivation |
LG Electronics Inc. |
| R2-2308201 |
Multicast servic continuity |
LG Electronics Inc. |
| R2-2308304 |
Discussion on multicast reception in RRC_INACTIVE CP issues |
CMCC |
| R2-2308343 |
Multicast reception in RRC_INACTIVE |
ZTE, Sanechips |
| R2-2308552 |
MBS multicast and UE power saving |
Ericsson |
| R2-2308558 |
Connection resumption triggering for more reliable MBS reception |
InterDigital Inc. |
| R2-2308568 |
Ensuring desired level of reliability for an MBS session in RRC_INACTIVE |
Interdigital Inc. |
| R2-2308649 |
MCCH Monitoring and Configuration of UE with Multicast reception in RRC_INACTIVE |
SHARP Corporation |
| R2-2308652 |
Support of SDT and Multicast in RRC_INACTIVE configured together |
SHARP Corporation |
| R2-2308850 |
PTM configuration for eMBS |
Shanghai Jiao Tong University, NERCDTV |
| R2-2308889 |
Multicast reception in RRC_INACTIVE |
Ericsson |
| 7.11.2.2 |
User plane |
|
| R2-2307086 |
User plane for multicast reception in RRC_INCTIVE stat |
TD Tech, Chengdu TD Tech |
| R2-2307110 |
Discussion on eMBS from the UP Perspective |
vivo |
| R2-2307136 |
L2 operation during state transitions and mobility for R18 multicast |
MediaTek inc. |
| R2-2307146 |
User plane aspects for eMBS |
NEC |
| R2-2307148 |
User plane for multicast reception in RRC_INCTIVE state |
TD Tech, Chengdu TD Tech |
| R2-2307264 |
Discussion on User Plane for Multicast reception in RRC_INACTIVE |
CATT, CBN |
| R2-2307494 |
UP issues for multicast reception for RRC INACTIVE UE |
Huawei, HiSilicon |
| R2-2307639 |
Further views on multicast CFR configuration aspects |
Qualcomm Incorporated |
| R2-2307758 |
UP Aspects for Multicast Reception in RRC_INACTIVE |
Samsung |
| R2-2307844 |
User plane aspects for multicast reception in RRC_INACTIVE |
Apple |
| R2-2307984 |
User plane aspects of multicast reception in RRC_INACTIVE state |
Nokia, Nokia Shanghai Bell |
| R2-2308014 |
User plane aspects of Multicast reception in RRC_INACTIVE |
Lenovo |
| R2-2308305 |
Discussion on multicast reception in RRC_INACTIVE UP issues |
CMCC |
| R2-2308344 |
CFR design for Multicast reception in RRC_INACTIVE |
ZTE, Sanechips |
| R2-2308535 |
MBS remaining issues on DRX |
Ericsson |
| R2-2308594 |
Discussion on UP issues for Multicast in RRC Inactive |
LG Electronics Inc. |
| R2-2308853 |
Discussion and draft TP on the PDCP operation for the support of multicast reception in RRC_INACTIVE state |
Beijing Xiaomi Software Tech |
| R2-2309271 |
PDCP Running CR for eMBS |
Xiaomi |
| 7.11.3 |
Shared processing for MBS broadcast and Unicast reception |
|
| R2-2307111 |
Further Discussion on Shared Processing in eMBS |
vivo |
| R2-2307265 |
Remaining Issues on Shared Processing |
CATT, CBN |
| R2-2307460 |
Discussion on shared process for MBS broadcast and unicast |
NEC Corporation |
| R2-2307495 |
Discussion on shared processing for MBS broadcast and unicast reception |
Huawei, HiSilicon |
| R2-2307596 |
Rel-18 MII Enhancements |
Samsung R&D Institute India |
| R2-2307640 |
Shared processing for MBS broadcast and Unicast reception |
Qualcomm Incorporated |
| R2-2307675 |
Discussion on the reporting signaling for shared MBS capability |
Xiaomi |
| R2-2308306 |
Discussion on shared processing |
CMCC |
| R2-2308345 |
Non-serving cell configuration update in case of shared processing |
ZTE, Sanechips |
| R2-2308744 |
Additional scenarios for shared processing |
Nokia, Nokia Shanghai Bell |
| R2-2309032 |
[Offline 601] Discussion report: Frequency and bandwidth signalling |
Qualcomm Incorporated |
| 7.12.1 |
Organizational |
|
| R2-2307269 |
Running CR for introduction of mobile IAB in TS 38.340 |
Huawei, HiSilicon |
| R2-2307602 |
Updated workplan for Rel-18 mobile IAB |
Qualcomm Inc. (Rapporteur) |
| R2-2307603 |
BL CR to TS 38.300 on Introduction to mobile IAB |
Qualcomm Inc. |
| R2-2308080 |
Draft CR of TS 38.304 for Rel-18 mIAB |
Intel Corporation |
| R2-2308447 |
RRC running CR for mobile IAB |
Ericsson |
| R2-2308452 |
Initial IAB MAC rapporteur views on potential MAC impact of RACH-less HO for mIAB |
Samsung |
| R2-2308823 |
38.306 running CR for mobile IAB capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2308824 |
38.331 running CR for mobile IAB capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2309280 |
Running CR for introduction of mobile IAB in TS 38.340 |
Huawei, HiSilicon |
| R2-2309282 |
RRC running CR for mobile IAB |
Ericsson |
| R2-2309328 |
38.304 CR for R18 mIAB |
Intel Corporation |
| R2-2309340 |
38.300 Running CR for mobile IAB |
Qualcomm |
| 7.12.2 |
Mobility Enhancements |
|
| R2-2307184 |
Discussion on mobility enhancements for mobile IAB |
CANON Research Centre France |
| R2-2308894 |
Discussion on mIAB mobility enhancements |
Samsung Electronics Czech |
| 7.12.2.1 |
Connected mode |
|
| R2-2307270 |
Connected mode enhancement for mobile IAB |
Huawei, HiSilicon |
| R2-2307604 |
Enhancements for mobile IAB connected mode mobility |
Qualcomm Inc. |
| R2-2307820 |
CONNECTED mobility enhancement in mobile IAB |
Apple |
| R2-2307822 |
UE on-board status identification and reporting |
Apple, Huawei, HiSilicon, Lenovo, CATT, InterDigital Inc. |
| R2-2307910 |
Discussion on mobility enhancements for mobile IAB |
NEC Corporation |
| R2-2308006 |
Mobility enhancements for mobile IAB-node and its connected UE |
Lenovo |
| R2-2308078 |
Mobile IAB mobility enhancement for connected UEs |
Intel Corporation |
| R2-2308097 |
Discussion on mobility enhancement for UE in connected mode |
ZTE, Sanechips |
| R2-2308444 |
Remaining issues for supporting RACH-less in mobile IAB |
Ericsson |
| R2-2308513 |
Conditional handover enhancement for mobile IAB |
Nokia, Nokia Shanghai Bell |
| R2-2308569 |
Connected mode mobility enhancements for mobile IAB |
Interdigital Inc. |
| R2-2308571 |
CHO and RACH-less HO for mobile IAB Scenario |
InterDigital Inc. |
| R2-2308603 |
Way forward for RACH-less HO in mobile IAB |
Nokia, Nokia Shanghai Bell, LG Electronics Inc. |
| R2-2308682 |
On the need of group mobility and other enhancements |
LG Electronics |
| R2-2308731 |
Connected mode mobility for mobile IAB |
CATT |
| R2-2308778 |
Enhancements for IAB-node mobility and onboard UEs |
AT&T |
| R2-2308940 |
Discussion on RACH-less handover |
Xiaomi |
| 7.12.2.2 |
Idle/Inactive mode |
|
| R2-2307271 |
Idle/Inactive mode mobility enhancement for mobile IAB |
Huawei, HiSilicon |
| R2-2307605 |
Enhancements for mobile IAB idle and inactive mode mobility |
Qualcomm Inc. |
| R2-2307738 |
Discussion on Mobile IAB mobility enhancements |
vivo |
| R2-2307821 |
Discussion on IDLE/INACTIVE UE mobility enhancement |
Apple |
| R2-2308079 |
UE cell (re)selection towards mobile IAB cell |
Intel Corporation |
| R2-2308098 |
Discussion on mobility enhancement for UE in idle or inactive mode |
ZTE, Sanechips |
| R2-2308110 |
IDLE/INACTIVE mode mobility enhancements for mobile IAB |
Kyocera |
| R2-2308164 |
Mobile IAB cell indication to UE behaviour |
Sony |
| R2-2308445 |
Behaviour for RRC_IDLE and RRC_INACTIVE UEs under a mIAB node |
Ericsson |
| R2-2308446 |
Indication of DU-migration to UEs in IDLE and INACTIVE |
Ericsson |
| R2-2308514 |
Cell reselection for UEs on board mobile IAB |
Nokia, Nokia Shanghai Bell |
| R2-2308570 |
IDLE/INACTIVE mobility enhancements for mobile IAB |
Interdigital Inc. |
| R2-2308581 |
UE cell reselection prioritization for mobile IAB |
Sharp |
| R2-2308683 |
Cell reselection enhancement and text proposal |
LG Electronics |
| R2-2308684 |
Access restiction for mIAB cell |
LG Electronics |
| R2-2308732 |
Idle mode mobility for mobile IAB (with TP to TS38.304/TS38.331) |
CATT |
| 7.12.3 |
Other |
|
| R2-2307272 |
RNAU issues for mobile IAB |
Huawei, HiSilicon |
| R2-2307606 |
Topology adaptation for mobile IAB-node |
Qualcomm Inc. |
| R2-2308007 |
Discussion on BAP and PCI collision issues for mobile IAB |
Lenovo |
| R2-2308049 |
BAP specification impact of redundant entries |
Samsung |
| R2-2308099 |
Discussion on remaining issues for mobile IAB |
ZTE, Sanechips |
| R2-2308165 |
PCI collision in mobile IAB |
Sony |
| R2-2308451 |
Interference mitigation and PCI collision |
Samsung |
| R2-2308733 |
BAP configuration impacts (with TP to TS38.340) |
CATT, Huawei, Qualcomm Incorporated |
| 7.13.1 |
Organizational |
|
| R2-2307022 |
LS on MRO for CPC and CPA and fast MCG recovery (R3-230992; contact: Huawei) |
RAN3 |
| R2-2307023 |
LS on potential override of logged MDT reports upon moving from SNPN to PLMN (R3-232118; contact: Ericsson) |
RAN3 |
| R2-2307024 |
LS on intra-system inter-RAT SHR and SPR (R3-232140; contact: Huawei) |
RAN3 |
| R2-2307025 |
Reply LS on RACH enhancement for R18 SONMDT (R3-232144; contact: Huawei) |
RAN3 |
| R2-2307030 |
LS on SHR and SPR (R3-233380; contact: Samsung) |
RAN3 |
| R2-2307069 |
Reply LS on user consent of Non-public Network (S3-231399; contact: Vodafone) |
SA3 |
| R2-2308428 |
LTE Running CR for Rel-18 SON MRO |
Ericsson |
| R2-2308429 |
Running CR for Rel-18 SON MRO |
Ericsson |
| R2-2308458 |
LTE Running CR for Rel-18 SON MRO |
Ericsson |
| R2-2308459 |
Running CR for Rel-18 SON MRO |
Ericsson |
| R2-2308501 |
Running 36.331 CR for SN RACH report |
ZTE Corporation, Sanechips |
| R2-2308502 |
Running 38331 CR for SON on RACH report |
ZTE Corporation, Sanechips |
| R2-2308623 |
Running 38.331 CR for logged MDT enhancements and NPN |
Huawei, HiSilicon |
| R2-2308624 |
Running 36.331 CR for logged MDT enhancements |
Huawei, HiSilicon |
| R2-2308801 |
Discussion on RAN2 impacts due to the LS R3-233380 |
Samsung, CMCC, Qualcomm |
| R2-2309021 |
[DRAFT] Response LS on SHR and SPR |
Nokia |
| R2-2309022 |
Response LS on SHR and SPR |
RAN2 |
| R2-2309028 |
[DRAFT] Response LS on SHR and SPR |
Nokia |
| 7.13.2 |
MRO for inter-system handover for voice fallback |
|
| R2-2308240 |
MRO for inter-system handover for voice fallback |
Samsung |
| R2-2308423 |
Discussion on voice fallback HO failure |
Ericsson |
| 7.13.3 |
MDT override |
|
| R2-2307411 |
Considerations on MDT override enhancement for E-UTRAN |
Beijing Xiaomi Software Tech |
| R2-2308503 |
Consideration on MDT override remaining issues |
ZTE Corporation, Sanechips |
| 7.13.4 |
SHR and SPCR |
|
| R2-2307283 |
Reply LS proposal to R2-2307030/R3-233380 |
Nokia, Nokia Shanghai Bell |
| R2-2307284 |
Inter-RAT SHR and SPR related issues |
Nokia, Nokia Shanghai Bell |
| R2-2307430 |
Remaining issues on SPR |
vivo |
| R2-2307707 |
Further discussion on SPR |
CATT |
| R2-2308015 |
Discussion on inter-RAT SHR from NR to LTE |
Lenovo |
| R2-2308016 |
SON enhancements for SPR |
Lenovo |
| R2-2308425 |
Discussion on inter-RAT SHR and SPR |
Ericsson |
| R2-2308496 |
SON/MDT enhancements for SHR and SPR |
Samsung |
| R2-2308504 |
Consideration on SHR and SPR remaining issues |
ZTE Corporation, Sanechips |
| R2-2308620 |
Remain issues on SPR |
SHARP Corporation |
| R2-2308629 |
Discussion on voice fallback, SHR and SPR |
Huawei, HiSilicon |
| R2-2308954 |
Pre-meeting summary of 7.13.4 |
Huawei, HiSilicon |
| R2-2308974 |
Pre-meeting summary of 7.13.4 |
Huawei, HiSilicon |
| 7.13.5 |
SON for NR-U |
|
| R2-2307708 |
SON Enhancement for NR-U |
CATT |
| R2-2308017 |
Discussion on MRO for NR-U |
Lenovo |
| R2-2308325 |
SONMDT enhancement for NR-U |
CMCC |
| R2-2308473 |
SON/MDT enhancements for NR-U |
Samsung |
| R2-2308505 |
Consideration on NR-U related SON |
ZTE Corporation, Sanechips |
| R2-2308625 |
Discussion on NR-U |
Huawei, HiSilicon |
| R2-2308897 |
Enhancements of SON reports for NR-U |
Ericsson |
| R2-2308899 |
[Post122][590][R18 SON/MDT] Open issues of SON NR-U (Ericsson) |
Ericsson |
| 7.13.6 |
RACH enhancement |
|
| R2-2307285 |
Discussion on RACH enhancement for SON |
Nokia, Nokia Shanghai Bell |
| R2-2307408 |
Consideration on the SON enhancements for RACH report |
Beijing Xiaomi Software Tech |
| R2-2307709 |
RACH enhancement for SON |
CATT |
| R2-2307797 |
Discussion on RACH enhancements |
ZTE Corporation, Sanechips |
| R2-2307825 |
RACH enhancements for slicing |
Apple |
| R2-2308241 |
SON/MDT enhancements for RACH |
Samsung |
| R2-2308291 |
Further Considerations on RACH Enhancement |
CMCC |
| R2-2308427 |
RA report enhancement |
Ericsson |
| R2-2308626 |
Discussion on RACH enhancement |
Huawei, HiSilicon |
| R2-2308654 |
Further Discussion on RACH Partitioning for SON |
China Telecom |
| R2-2308960 |
Summary of 7.13.6 RACH enhancement SONMDT (Nokia) |
Nokia (Rapporteur) |
| 7.13.7 |
SON/MDT enhancements for Non-Public Networks |
|
| R2-2307286 |
Discussion on open NPN issues in SON/MDT |
Nokia, Nokia Shanghai Bell |
| R2-2307409 |
Discussion on the SONMDT enhancement for NPN |
Beijing Xiaomi Software Tech |
| R2-2307410 |
Discussion on the “LS on potential override of logged MDT reports upon moving from SNPN to PLMN” from RAN3 (R3-232118) |
Beijing Xiaomi Software Tech |
| R2-2307431 |
Discussion on SON enhancements for NPN |
vivo |
| R2-2307710 |
SON and MDT Enhancement for NPN |
CATT |
| R2-2307798 |
Discussion on SON-MDT support for NPN |
ZTE Corporation, Sanechips |
| R2-2307826 |
Out-of-coverage in NPN |
Apple |
| R2-2308245 |
SON/MDT enhancements for NPN |
Samsung |
| R2-2308426 |
SON Support for NPN |
Ericsson |
| R2-2308627 |
Discussion on SONMDT enhancements for NPN |
Huawei, HiSilicon |
| R2-2309023 |
Summary of 7.13.7 SONMDT enhancements for NPN (CATT) |
CATT |
| 7.13.8 |
Other |
|
| R2-2307287 |
MRO enhancements for Fast MCG recovery and for MR-DC CPAC |
Nokia, Nokia Shanghai Bell |
| R2-2307288 |
Improvement of handling of timeConnFailure |
Nokia, Nokia Shanghai Bell |
| R2-2307432 |
Discussion on MRO for CPAC |
vivo |
| R2-2307679 |
Discussion on CPAC failure report |
NTT DOCOMO, INC. |
| R2-2307680 |
Discussion on fast MCG recovery failure |
NTT DOCOMO, INC. |
| R2-2307711 |
Discussion on Fast MCG recovery MRO Enhancement |
CATT |
| R2-2307712 |
Discussion on MHI Enhancement for SCG Deactivation/Activation |
CATT |
| R2-2308018 |
SON enhancements for CPAC |
Lenovo |
| R2-2308019 |
MRO for fast MCG link recovery |
Lenovo |
| R2-2308326 |
Summary of [Post122][584][R18 SON/MDT] Open issues on fast MCG recovery |
CMCC |
| R2-2308327 |
SON MDT enhancement for MR-DC CPAC |
CMCC |
| R2-2308328 |
MHI Enhancement for SCG Activation/Deactivation |
CMCC, Ericsson, CATT |
| R2-2308424 |
Discussion on Fast MCG recovery and SCG failure optimization |
Ericsson |
| R2-2308490 |
Fast MCG Link Recovery Optimization |
Samsung |
| R2-2308506 |
Consideration on other SON issues |
ZTE Corporation, Sanechips |
| R2-2308621 |
Discussion on MRO for CPAC |
SHARP Corporation |
| R2-2308622 |
MRO for fast MCG recovery |
SHARP Corporation |
| R2-2308628 |
Discussion on Fast MCG recovery and CPAC |
Huawei, HiSilicon |
| R2-2308630 |
Discussion on UE capability |
Huawei, HiSilicon |
| R2-2309024 |
Summary of 7.13.8 Other |
ZTE Corporation, Sanechips |
| 7.14.1 |
Organizational |
|
| R2-2307074 |
Reply LS on buffer level threshold-based RVQoE reporting (S4-231119; contact: Apple) |
SA4 |
| R2-2307966 |
Running CR for QoE measurements |
Ericsson |
| R2-2308231 |
37.340 Running CR to support QoE in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2308869 |
Revised Work Plan for Rel-18 NR QoE Enhancement |
China Unicom |
| R2-2308872 |
38.300 running CR for R18 QoE enhancement in NR |
China Unicom, Huawei, HiSilicon |
| R2-2309314 |
38.300 running CR for R18 QoE enhancement in NR |
China Unicom, Huawei, HiSilicon |
| R2-2309332 |
Running CR for QoE enhancement to support QoE in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2309337 |
Running CR for QoE enhancements in NR |
Ericsson |
| 7.14.2 |
QoE measurements in RRC_IDLE INACTIVE |
|
| R2-2307618 |
Discussion on support of QoE measurements in RRC_IDLE and RRC_INACTIVE |
Lenovo |
| R2-2307746 |
Open issues on QoE collection for IDLE and Inactive state |
Qualcomm Incorporated |
| R2-2307793 |
Discussion on QoE measurement in IDLE and INACTIVE |
ZTE Corporation, Sanechips |
| R2-2307834 |
QoE Measurements Discarding in IDLE/INACTIVE States |
Apple |
| R2-2307926 |
Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE |
Samsung |
| R2-2307967 |
QoE measurements in RRC_INACTIVE and RRC_IDLE |
Ericsson |
| R2-2308232 |
QoE for RRC IDLE and RRC INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2308312 |
Discusson on QoE in RRC_IDLE and RRC_INACTIVE |
CMCC |
| R2-2308354 |
Discussion on QoE measurements in RRC IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2308361 |
Discussion on QoE measurements in RRC IDLE and INACTIVE state |
CATT |
| R2-2308871 |
Discussion on QoE measurements in RRC_IDLE and INACTIVE states |
China Unicom |
| R2-2309004 |
LS on QoE in RRC IDLE/INACTIVE and NR-DC scenarios |
RAN2 |
| R2-2309031 |
[DRAFT] LS on QoE in RRC IDLE/INACTIVE and NR-DC scenarios |
Huawei |
| 7.14.3 |
Rel-17 leftover topics for QoE |
|
| R2-2307473 |
Discussion on buffer level threshold based triggering |
NEC |
| R2-2307747 |
Discussion on QoS flow ID(s) reporting and threshold-based Buffer Level reporting |
Qualcomm Incorporated |
| R2-2307794 |
Discussion on Rel-17 leftover issues for QoE |
ZTE Corporation, Sanechips |
| R2-2307835 |
Views on Buffer Level Threshold Based RVQoE Reporting |
Apple |
| R2-2307927 |
Discussion on buffer level threshold based triggering |
Samsung |
| R2-2307969 |
Event based RVQoE reporting |
Ericsson |
| R2-2308233 |
Discussion on Rel-17 leftovers |
Nokia, Nokia Shanghai Bell |
| R2-2308313 |
Discusson on Rel-17 leftover topics for QoE |
CMCC |
| R2-2308356 |
Discussion on Rel-17 left-over issues |
Huawei, HiSilicon |
| R2-2308362 |
Discussion on Rel-17 leftover topics for QoE |
CATT |
| 7.14.4 |
Support of QoE measurements for NR-DC |
|
| R2-2307474 |
Discussion on QoE measurements for MR-DC |
NEC |
| R2-2307748 |
Open issues to support QoE collection in NR-DC |
Qualcomm Incorporated |
| R2-2307795 |
Discussion on QoE measurement for NR-DC |
ZTE Corporation, Sanechips |
| R2-2307836 |
Discussions on QoE Reporting for NR-DC |
Apple |
| R2-2307928 |
Discussion on QoE measurement in NR-DC |
Samsung |
| R2-2307968 |
QoE measurements in NR-DC |
Ericsson |
| R2-2308234 |
On QoE configuration and reporting in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2308314 |
Discussion on QoE in NR-DC |
CMCC |
| R2-2308355 |
Discussion on QoE measurements in NR-DC |
Huawei, HiSilicon |
| R2-2308363 |
Discussion on support of QoE measurement for NR-DC |
CATT |
| R2-2308870 |
Discussion on QoE configuration and reporting for NR-DC |
China Unicom |
| 7.14.5 |
UE capabilities and other topics |
|
| R2-2307749 |
Discussion on UE QoE capabilities |
Qualcomm Incorporated |
| R2-2307796 |
Discussion on Rel-18 other QoE enhancement |
ZTE Corporation, Sanechips |
| R2-2307837 |
Views on UE Capabilities for Rel-18 QoE |
Apple |
| R2-2307929 |
Discussion on QoE measurement continuity during inter-RAT handover |
Samsung |
| R2-2307970 |
Outstanding issue and UE capabilities for QoE |
Ericsson |
| R2-2308235 |
Inter-RAT QoE continuity and UE capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2308315 |
Discussion on QoE UE capabilities |
CMCC |
| R2-2308357 |
Discussion on UE capabilities for QoE enhancements |
Huawei, HiSilicon |
| 7.15.1 |
Organizational |
|
| R2-2307060 |
Reply LS on carrier mapping for unicast SL CA (S2-2307794; contact: LGE) |
SA2 |
| R2-2307087 |
Work plan of R18 SL-Evo |
OPPO, LG |
| R2-2307088 |
Running CR of TS 38.331 for SL Evolution |
OPPO |
| R2-2307200 |
Stage-3 Running CR of TS 38.321 for SL Evolution |
LG |
| R2-2307976 |
Further Discussion on SA2 Reply LS on SL CA |
vivo |
| R2-2308519 |
Rapporteur Revision to Stage 2 Running CR of TS 38.300 for SL Evolution |
InterDigital France R&D, SAS |
| R2-2309140 |
Stage 2 Running CR of TS 38.300 for SL Evolution |
InterDigital |
| R2-2309151 |
Running CR of TS 38.331 for SL Evolution |
OPPO (Rapporteur) |
| R2-2309152 |
Stage-3 Running CR of TS 38.321 for SL Evolution |
LG |
| R2-2309326 |
Running CR of TS 38.331 for SL Evolution |
OPPO (Rapporteur) |
| 7.15.2 |
SL-U: SL Consistent LBT failure |
|
| R2-2307089 |
Discussion on C-LBT |
OPPO |
| R2-2307130 |
Discussion on SL consistent LBT failure |
Huawei, HiSilicon |
| R2-2307214 |
Discussion on SL consistent LBT failure |
LG Electronics Inc. |
| R2-2307383 |
Discussion on remaining issues of SL-U |
NEC |
| R2-2307385 |
(draft)LS to RAN1 on LBT failure indication |
NEC |
| R2-2307478 |
Discussion on Sidelink consistent LBT failure |
ZTE Corporation, Sanechips |
| R2-2307555 |
Further Discussion on SL LBT |
CATT |
| R2-2307723 |
Discussion on SL consistent LBT failure |
Xiaomi |
| R2-2307816 |
Remaining issues on SL consistent LBT failure recovery |
Apple |
| R2-2307956 |
Remaining details of SL LCP and SL consistent LBT procedure |
Lenovo |
| R2-2307977 |
Remaining issues on SL consistent LBT failure |
vivo |
| R2-2308085 |
On SL-U LBT failure |
Intel Corporation |
| R2-2308117 |
Remaining issues on SL-U consistent LBT failure |
Spreadtrum Communications |
| R2-2308375 |
Remaining Issues on LBT Failure for SL Unlicensed |
InterDigital |
| R2-2308462 |
Remaining issues for SL C-LBT |
Samsung |
| R2-2308515 |
Open issues on consistent LBT handling and recovery |
Nokia, Nokia Shanghai Bell |
| R2-2308582 |
Discussion on SL C-LBT failure |
Qualcomm India Pvt Ltd |
| R2-2308699 |
Remaining issue on SL Consistent LBT failure |
ITL |
| R2-2309157 |
LS on SL RB set index and LBT failure indication for PSFCH |
RAN2 |
| 7.15.3 |
SL-U: SL resource (re)selection, SL LCP |
|
| R2-2307090 |
Discussion on Resource (Re)selection and LCP Enhancement |
OPPO |
| R2-2307131 |
Consideration on SL resource selection and LCP enhancement |
Huawei, HiSilicon |
| R2-2307145 |
Consideration on MCSt impact |
NEC |
| R2-2307215 |
Discussion on SL resource (re)selection and LCP impact |
LG Electronics Inc. |
| R2-2307479 |
Discussion on resource (re)selection and LCP for SL-U |
ZTE Corporation, Sanechips |
| R2-2307556 |
Discussion on Sidelink Resource Reselection |
CATT |
| R2-2307724 |
Discussion on resource allocation and enhanced LCP for SL-U |
Xiaomi |
| R2-2307817 |
Remaining issues on LCP and resource (re)selection in SL-U |
Apple |
| R2-2307903 |
LCP enhancement for COT sharing |
Ericsson, Xiaomi, Nokia, Nokia Shanghai Bell, vivo |
| R2-2307904 |
Resource selection and reselection for SL-U |
Ericsson |
| R2-2307978 |
Remaining issues on resource (re)selection and LCP |
vivo |
| R2-2307992 |
Discussion on resource (re)selection for NR SL-U |
Lenovo |
| R2-2308084 |
On resource reselection and enhanced LCP |
Intel Corporation |
| R2-2308118 |
Discussion on resource (re)selection and SL LCP in SL-U |
Spreadtrum Communications |
| R2-2308376 |
Implementing LCP for SL Unlicensed |
InterDigital |
| R2-2308377 |
Mode 2 Resource Selection Considering LBT Impacts |
InterDigital |
| R2-2308463 |
SL resource (re)selection with intra-UE LBT impact |
Samsung |
| R2-2308516 |
Open issues on resource (re)selection and LCP restrictions |
Nokia, Nokia Shanghai Bell |
| R2-2308590 |
Discussion on SL resource selection and LCP |
Qualcomm India Pvt Ltd |
| R2-2308725 |
Discussion on resource (re)selection for MCSt |
ASUSTeK |
| R2-2309154 |
Summary of [512][V2X SL] COT sharing for mode 1 (Ericsson) |
Ericsson |
| 7.15.4 |
SL-U: Others |
|
| R2-2307132 |
Impact on leftover issues for SL-U |
Huawei, HiSilicon |
| R2-2307175 |
Sidelink LBT Failure and Acknowledgement on PUCCH |
Samsung Electronics Co., Ltd |
| R2-2307216 |
Discussion on SL-U others |
LG Electronics Inc. |
| R2-2307480 |
Discussion on SL CG and DRX in SL-U |
ZTE Corporation, CAICT, Sanechips |
| R2-2307557 |
Other Remaining Issues in SL-U |
CATT |
| R2-2307725 |
Discussion on other aspects for SL-U |
Xiaomi |
| R2-2307906 |
Other aspects on SL-U |
Ericsson |
| R2-2307993 |
Other remaining issue for NR SL-U |
Lenovo |
| R2-2308464 |
Other issues for SL-U |
Samsung |
| R2-2308517 |
On HARQ DTX and multiple PSFCH occasions |
Nokia, Nokia Shanghai Bell |
| R2-2308698 |
Remaining issue on SL DRX in SL-U |
ITL |
| 7.15.5 |
SL-FR2 |
|
| R2-2307213 |
Discussion on RAN2 aspects of SL-FR2 |
LG Electronics Inc. |
| R2-2307229 |
Discussion on SL-FR2 impact to RAN2 |
Xiaomi |
| R2-2307236 |
Discussion on SL-FR2 impact |
OPPO |
| R2-2307262 |
Discussion on sidelink FR2 aspects in RAN2 |
Nokia Netherlands |
| R2-2307481 |
Discussion on sidelink FR2 |
ZTE Corporation, CAICT, Sanechips |
| R2-2307501 |
RAN2 Aspects of NR Sidelink Operation in FR2 |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2307558 |
Discussion on Sidelink Operation on FR2 |
CATT |
| R2-2307573 |
Discussion on SL-FR2 |
Huawei, HiSilicon |
| R2-2307818 |
Discussion on RAN2 aspects of SL FR2 |
Apple |
| R2-2307905 |
SL in FR2 |
Ericsson |
| R2-2307979 |
Discussion on BFD BFR and RLF |
vivo |
| R2-2307994 |
Discussion on FR2 operation for NR SL |
Lenovo |
| R2-2308465 |
Discussion on SL-FR2 |
Samsung |
| R2-2308591 |
Discussion on SL FR2 |
Qualcomm India Pvt Ltd |
| 7.15.6 |
SL-CA |
|
| R2-2307091 |
Discussion on Carrier Aggregation |
OPPO |
| R2-2307092 |
Discussion on ’TX Profile’ |
OPPO, Nokia, Nokia Shanghai Bell, vivo, NEC, MediaTek Inc., Samsung |
| R2-2307201 |
Discussion on remaining issues of SL-CA enhancements |
LG Electronics Inc. |
| R2-2307353 |
Discussion on CSI report for Carrier Aggregation |
SHARP Corporation |
| R2-2307384 |
Discussion on remaining issues of SL CA |
NEC |
| R2-2307404 |
SL RLF in SL CA |
Fujitsu |
| R2-2307482 |
Discussion on sidelink CA |
ZTE Corporation, Sanechips |
| R2-2307559 |
Discussion on NR Sidelink CA |
CATT |
| R2-2307574 |
Discussion on SL CA enhancements |
Huawei, HiSilicon |
| R2-2307718 |
SL CA for unicast |
TCL |
| R2-2307726 |
Discussion on carrier aggregation for NR sidelink |
Xiaomi |
| R2-2307819 |
Further discussion on Sidelink CA |
Apple |
| R2-2307859 |
Discussion on TX profile for SL CA GC/BC |
Apple,Ericsson, Qualcomm, Xiaomi, ZTE, Sanechips, Philips, LG Electronics, InterDigital |
| R2-2307907 |
Aspects of SL CA |
Ericsson |
| R2-2307975 |
Further discussion on the support of CA for NR Sidelink Mode-2 |
vivo |
| R2-2307995 |
Discussion on multi-carrier operation for NR SL |
Lenovo |
| R2-2308378 |
Considering Survival Time Requirement for SL |
InterDigital, Lenovo |
| R2-2308379 |
Carrier Aggregation for NR SL for Unicast |
InterDigital |
| R2-2308466 |
Remaining issues for SL CA |
Samsung |
| R2-2308592 |
Discussion on SL CA |
Qualcomm India Pvt Ltd |
| R2-2308747 |
Support of NR SL CA |
Nokia, Nokia Shanghai Bell |
| R2-2308979 |
Discussion on TX profile for SL CA GC/BC |
Apple, Ericsson, Qualcomm, Xiaomi, ZTE, Sanechips, Philips, LG Electronics, InterDigital, Bosch |
| R2-2309119 |
Reply LS to SA2 on Sidelink positioning procedure |
RAN2 |
| R2-2309155 |
LS to SA2 on TX Profile for SL CA |
RAN2 |
| R2-2309156 |
Reply LS on carrier mapping for unicast SL CA |
RAN2 |
| R2-2309228 |
Reply LS to SA2 on assistance information provided to UE |
RAN2 |
| 7.16.1 |
Organizational |
|
| R2-2308912 |
R2 input to TR 38.843 |
Ericsson |
| R2-2308913 |
[Post122][059][AIML]: on functional framework, topics to discuss, and FFSs |
Ericsson |
| 7.16.2.1 |
Architecture and General |
|
| R2-2307140 |
General aspects of AIML framework |
NEC |
| R2-2307157 |
General aspects for AIML |
OPPO |
| R2-2307230 |
Discussion on architecture aspects |
Xiaomi |
| R2-2307364 |
Further discussions on architecture general aspects of AIML for NR air-interface |
CATT, Turkcell |
| R2-2307433 |
Discussion on Architecture General |
vivo |
| R2-2307484 |
Discussion on AI/ML Capability Reporting and Model LCM |
SHARP Corporation |
| R2-2307523 |
AI/ML functionality-based and model-ID based LCM |
Samsung R&D Institute UK |
| R2-2307684 |
AI/ML locality and capability: RAN2 impact |
Intel Corporation |
| R2-2307812 |
Discussion on UE capability, applicability condition reporting and LCM |
Apple |
| R2-2307813 |
Remaining issues on Model ID and AI/ML architecture |
Apple |
| R2-2308020 |
Discussion on identifier used for UE side/part model LCM |
Lenovo |
| R2-2308129 |
Discussion on general architecture |
Spreadtrum Communications |
| R2-2308150 |
AI/ML LCM Dependency on gNB Configuration |
MediaTek Inc. |
| R2-2308176 |
On Other Aspects of AI/ML for positioning accuracy enhancement |
Sony |
| R2-2308195 |
AIML architecture |
Nokia, Nokia Shanghai Bell, T-Mobile US, Samsung |
| R2-2308286 |
Report of [Post122][060][AIML] Mapping of functions to physical entities (CMCC) |
CMCC |
| R2-2308456 |
Discussion on the architectural and general aspects of AI/ML |
Futurewei Technologies |
| R2-2308548 |
AI/ML capability reporting |
InterDigital |
| R2-2308596 |
Discussion on AI/ML Architecture General |
Qualcomm Incorporated |
| R2-2308631 |
Discussion on general aspects |
Huawei, HiSilicon |
| R2-2308764 |
Consideration of Meta information and signalling framework |
Kyocera |
| R2-2308779 |
Architecture and LCM aspects of AI/ML for NR air interface |
AT&T |
| R2-2308795 |
AIML method_Architecture General |
LG Electronics |
| R2-2308836 |
Further Discussion on general aspects of AIML for PHY |
ZTE Corporation, Sanechips |
| R2-2308868 |
Discussion on Architecture and General |
TCL |
| R2-2308873 |
Discussion on the AI Functional Framework |
China Unicom |
| R2-2308914 |
On UE capability/applicability reporting and functionality-to-entity mapping |
Ericsson |
| R2-2309199 |
Discussion on AI/ML Architecture General |
Qualcomm Incorporated |
| R2-2309202 |
Summary report of [AT123][001][AIML] UE capability and applicability conditions (Apple) |
Apple |
| 7.16.2.2 |
Data Collection |
|
| R2-2307141 |
Requirements and Assumptions for AIML Data Collection |
NEC |
| R2-2307231 |
Discussion on data collection |
Xiaomi |
| R2-2307365 |
Considerations on data collection of AIML for NR air-interface |
CATT, Turkcell |
| R2-2307405 |
Discussions on AIML data collection |
Fujitsu |
| R2-2307434 |
Remaining issues of data collection for model training at server |
vivo, Qualcomm Incorporated |
| R2-2307521 |
Enhancements for RRM/MDT for AI/ML data collection |
Samsung R&D Institute UK |
| R2-2307814 |
Remaining issues on data collection for AI/ML |
Apple |
| R2-2308021 |
Qualitative analysis on data collection requirements |
Lenovo |
| R2-2308130 |
Discussion on data collection |
Spreadtrum Communications |
| R2-2308151 |
Data Collection for Model Training at UE Side |
MediaTek Inc. |
| R2-2308166 |
Some considerations about data collection |
Sony |
| R2-2308197 |
AIML data collection |
Nokia, Nokia Shanghai Bell |
| R2-2308410 |
Data collection for AIML |
Interdigital Inc. |
| R2-2308565 |
Data collection for AIML |
Interdigital Inc. |
| R2-2308632 |
Discussion on data collection |
Huawei, HiSilicon |
| R2-2308780 |
Data collection aspects of AI/ML for NR air interface |
AT&T |
| R2-2308796 |
AIML method_Data Collection |
LG Electronics |
| R2-2308837 |
Further Discussion On Purpose Driven Data Collection |
ZTE Corporation, Sanechips |
| R2-2308867 |
Data collection for AIML methods |
TCL |
| R2-2308898 |
Data collection for AI/ML |
Ericsson |
| 7.16.2.3 |
Model transfer – delivery |
|
| R2-2307142 |
AIML Data Collection for Model Training |
NEC |
| R2-2307143 |
AIML Model transfer |
NEC |
| R2-2307158 |
Open Issue Discussion on Model Transfer Delivery |
OPPO |
| R2-2307247 |
AI/ML model delivery |
Xiaomi |
| R2-2307366 |
Further discussions on AIML model transfer |
CATT, Turkcell |
| R2-2307435 |
Discussion on model transfer |
vivo |
| R2-2307520 |
AI/ML model transfer/delivery solutions |
Samsung R&D Institute UK |
| R2-2307685 |
Architecture impact on model transfer method |
Intel Corporation |
| R2-2307815 |
Further discussion on model transfer |
Apple |
| R2-2308022 |
Discussion on gNB/LMF awareness of UE side model and functionality |
Lenovo |
| R2-2308131 |
Discussion on model transfer-delivery |
Spreadtrum Communications |
| R2-2308178 |
Discussion on AI/ML Model Transfer/Delivery |
MediaTek Inc. |
| R2-2308199 |
AIML model transfer delivery |
Nokia, Nokia Shanghai Bell |
| R2-2308292 |
Discussion on AI/ML model transfer/delivery |
CMCC |
| R2-2308411 |
Way forward for AIML Model transfer/delivery |
Interdigital Inc. |
| R2-2308566 |
Way forward for AIML Model transfer/delivery |
Interdigital Inc. |
| R2-2308597 |
Discussion on Model Transfer/Delivery |
Qualcomm Incorporated |
| R2-2308633 |
Discussion on model transfer and delivery |
Huawei, HiSilicon |
| R2-2308781 |
AI/ML model transfer and delivery |
AT&T |
| R2-2308838 |
Further Discussion on Model TransferDelivery for AIML |
ZTE Corporation, Sanechips |
| R2-2308915 |
On the need for model transfer |
Ericsson |
| R2-2309200 |
Discussion on Model Transfer/Delivery |
Qualcomm Incorporated |
| 7.16.2.4 |
Control and LCM other |
|
| R2-2307159 |
Discussion on Model Monitoring |
OPPO |
| R2-2307160 |
Discussion on Model Identification |
OPPO |
| R2-2307367 |
Considerations on other model control procedures |
CATT, Turkcell |
| R2-2307436 |
Discussion on model management and identification |
vivo |
| R2-2307486 |
Discussion on Model Monitoring and Reporting Considering Functionality and Model ID based LCM |
SHARP Corporation |
| R2-2307522 |
Indication of supported AI/ML models and functionalities |
Samsung R&D Institute UK |
| R2-2307686 |
model control procedure: RAN2 impact |
Intel Corporation |
| R2-2307982 |
AI ML model management across RRC state transitions and mobility among non-interoperable networks |
Rakuten Symphony |
| R2-2308132 |
Discussion on Control and LCM other |
Spreadtrum Communications |
| R2-2308167 |
Some considerations about CSI compression |
Sony |
| R2-2308189 |
Model Control and Model Monitoring |
MediaTek Inc. |
| R2-2308212 |
AIML control and other topics |
Nokia, Nokia Shanghai Bell |
| R2-2308267 |
AI/ML model inference and monitoring for positioning accuracy enhancement |
Xiaomi |
| R2-2308293 |
Discussion on model control and other LCM procedures |
CMCC |
| R2-2308457 |
Discussion on the life cycle management of AI/ML models |
Futurewei Technologies |
| R2-2308549 |
Functionality ID for AI/ML control |
InterDigital |
| R2-2308598 |
Discussion on Life Cycle Management |
Qualcomm Incorporated |
| R2-2308634 |
Discussion on control and LCM other |
Huawei, HiSilicon |
| R2-2308782 |
AI/ML model control |
AT&T |
| R2-2308783 |
Discussion on model model-based management |
LG Electronics France |
| R2-2308839 |
Consideration on General Porocedure For Different Use Cases |
ZTE Corporation, Sanechips |
| R2-2308916 |
Control and monitoring responsibility |
Ericsson |
| R2-2309201 |
Discussion on Life Cycle Management |
Qualcomm Incorporated |
| 7.17.1 |
Organizational |
|
| R2-2307538 |
37.340 Running CR for Introduction of MUSIM |
ZTE Corporation, Sanechips |
| R2-2307689 |
Running RRC CR for NR MUSIM enhancements |
vivo |
| R2-2308726 |
38.300 Running Stage-2 CR for NR MUSIM enhancements |
China Telecom |
| R2-2309307 |
Running RRC CR for NR MUSIM enhancements |
vivo |
| R2-2309317 |
37.340 running CR for introduction of DualTxRx_MUSIM |
ZTE Corporation, Sanechips |
| R2-2309331 |
38.300 Running CR for NR MUSIM enhancements |
China Telecom |
| 7.17.2 |
Procedures for MUSIM temporary capability restriction |
|
| R2-2307161 |
Discussion on proactive and reactive approaches |
OPPO |
| R2-2307162 |
Discussion on early MUSIM Indication |
OPPO |
| R2-2307280 |
Procedures for MUSIM temporary capability restriction |
DENSO CORPORATION |
| R2-2307450 |
Discussion on early MUSIM indication |
Huawei, HiSilicon |
| R2-2307454 |
Discussion on proactive and reactive approaches |
Huawei, HiSilicon |
| R2-2307539 |
Consideration on the Temporary capability Reporting procedure |
ZTE Corporation, Sanechips |
| R2-2307690 |
Early indication for MUSIM temporary capability restriction |
vivo |
| R2-2307691 |
Procedures for MUSIM temporary capability restriction |
vivo |
| R2-2307774 |
Basic signalling procedure for reactive and proactive approach for Dual TX/TX MUSIIM operation |
Nokia, Nokia Shanghai Bell |
| R2-2307775 |
Additional aspects for Dual TX/RX MUSIM Operation |
Nokia, Nokia Shanghai Bell |
| R2-2307780 |
Indication of UE Capability Restriction for eMUSIM |
SHARP Corporation |
| R2-2307872 |
Signalling aspects for MUSIM temporary capability restriction |
Apple |
| R2-2308089 |
Common framework for proactive and reactive approach for MUSIM |
Intel Corporation |
| R2-2308091 |
MUSIM Capability restriction signalling during RRC Resume and Setup |
Intel Corporation |
| R2-2308243 |
Discussion on early capability restriction indication |
NEC |
| R2-2308244 |
Procedures for MUSIM temporary capability restriction |
NEC |
| R2-2308255 |
Early indication of restricted capabilities for MUSIM UE |
Ericsson |
| R2-2308497 |
Early indication of temporary capability restriction |
Samsung |
| R2-2308498 |
Discussion on temporary capability restriction |
Samsung |
| R2-2308758 |
Procedure for MUSIM temporary capability restriction |
China Telecom |
| R2-2308787 |
General procedure for Both Proactive and Reactive cases |
LG Electronics |
| R2-2308788 |
Supporting Proactive cases in other scenarios |
LG Electronics |
| R2-2308789 |
Timer based approach in MUSIM |
LG Electronics |
| R2-2308791 |
Procedures for Dual-Active MUSIM |
Qualcomm Incorporated |
| 7.17.3 |
Allowed MUSIM temporary capability restrictions |
|
| R2-2307163 |
Allowed MUSIM temporary capability restrictions |
OPPO |
| R2-2307451 |
Details of allowed MUSIM temporary capability restrictions |
Huawei, HiSilicon |
| R2-2307540 |
Consideration on the Temporory Capability Reporting |
ZTE Corporation, Sanechips |
| R2-2307598 |
Allowed MUSIM temporary capability restrictions |
Samsung R&D Institute India |
| R2-2307678 |
Capability sharing issue for SRS Tx switching capability |
Xiaomi |
| R2-2307692 |
Discussion on temporary capability restriction for Rel-18 Multi-SIM |
vivo |
| R2-2307776 |
Analysis on capability restriction for Dual TX/RX MUSIM Operation |
Nokia, Nokia Shanghai Bell |
| R2-2307873 |
Allowed MUSIM temporary capability restriction for band conflict mitigation |
Apple |
| R2-2308257 |
Discussion on frequencies restriction for MUSIM UE |
Ericsson |
| R2-2308258 |
Measurement gap capability for MUSIM UE |
Ericsson |
| R2-2308941 |
Discussion on frequencies restriction for MUSIM UE |
Ericsson |
| 7.17.4 |
Other |
|
| R2-2307452 |
Discussion on MUSIM gap priority |
Huawei, HiSilicon |
| R2-2307541 |
Consideration on the MUSIM Gap Priority |
ZTE Corporation, Sanechips |
| R2-2307542 |
Consideration on the R17/18 MUSIM Feature interaction |
ZTE Corporation, Sanechips |
| R2-2307693 |
Discussion on MUSIM gap priorities |
vivo |
| R2-2307777 |
On MUSIM Gap Priority handling for Single RX MUSIM operation |
Nokia, Nokia Shanghai Bell |
| R2-2308090 |
UAI repetition for MUSIM and dependency on Rel-17 MUSIM capability |
Intel Corporation |
| R2-2308256 |
MUSIM gap priority configuration |
Ericsson |
| R2-2308708 |
Further discussion on MUSIM gap priorities |
Samsung Electronics Nordic AB |
| R2-2308790 |
MUSIM Gap Priority |
LG Electronics |
| R2-2309001 |
LS to RAN4 on MUSIM gap priorities |
RAN2 |
| R2-2309008 |
LS to RAN4 on MUSIM gap priorities |
RAN2 |
| R2-2309278 |
LS to RAN4 on MUSIM gap priorities |
RAN2 |
| 7.18.1 |
Organizational |
|
| R2-2307128 |
Introduction of MT-SDT to MAC spec |
Huawei, HiSilicon |
| R2-2307129 |
Summary of [Post122][309][MT-SDT] 38.321 Running CR (Huawei) |
Huawei, HiSilicon |
| R2-2307529 |
RRC Running CR review report (Post122 email 312) |
ZTE Corporation (rapporteur) |
| R2-2307530 |
Introduction of MT-SDT |
ZTE Corporation (rapporteur) |
| R2-2308082 |
UE capabilities for Rel-18 MT-SDT WI |
Intel Corporation |
| R2-2308083 |
UE capabilities for Rel-18 MT-SDT WI |
Intel Corporation |
| R2-2308926 |
Introduction of MT-SDT in Stage-2 |
Nokia, Nokia Shanghai Bell |
| R2-2309141 |
Report of [AT123][301][MT-SDT] 38.331 Running CR (ZTE) |
ZTE Corporation (rapporteur) |
| R2-2309284 |
Introduction of MT-SDT |
ZTE Corporation (rapporteur) |
| R2-2309285 |
Introduction of MT-SDT to MAC spec |
Huawei, HiSilicon |
| R2-2309287 |
Introduction of MT-SDT in Stage-2 |
Nokia, Nokia Shanghai Bell |
| 7.18.2 |
Control plane aspects |
|
| R2-2307117 |
Remaining Issues on MT-SDT from CP |
vivo |
| R2-2307173 |
Remaining Control plane issues of MT SDT Procedure in RRC_INACTIVE state |
Samsung Electronics Co., Ltd |
| R2-2307518 |
CP aspects for MT-SDT procedure |
Nokia, Nokia Shanghai Bell |
| R2-2307672 |
RRC configuration and the UE capability for MT-SDT |
Xiaomi |
| R2-2307803 |
Consideration on MT-SDT from CP perspective |
LG Electronics Inc. |
| R2-2307845 |
Control plane aspects of MT-SDT |
Apple |
| R2-2307952 |
Further MT-SDT discussion |
Ericsson |
| R2-2307959 |
remaining CP details for MT-SDT |
Lenovo |
| R2-2308077 |
MT SDT – CP Open Topics on Capabilities and Configurations (including CG-SDT) |
Intel Corporation |
| R2-2308170 |
Control plane aspects for MT-SDT |
Sony |
| R2-2308349 |
Control plane aspects of MT-SDT |
Huawei, HiSilicon |
| R2-2308364 |
The remaining issues on CP aspects for MT-SDT |
CATT |
| R2-2308405 |
Remining issues on control plane aspects of MT-SDT |
Qualcomm Incorporated |
| R2-2308655 |
Discussion on CP aspects of MT-SDT |
China Telecom |
| 7.18.3 |
User plane aspects |
|
| R2-2307118 |
Remaining Issues on MT-SDT from UP |
vivo |
| R2-2307174 |
Remaining user plane issues of MT SDT Procedure in RRC_INACTIVE state |
Samsung Electronics Co., Ltd |
| R2-2307273 |
Discussion on user plane issues for MT-SDT |
Continental Automotive |
| R2-2307804 |
Remaining UP issues on MT-SDT |
LG Electronics Inc. |
| R2-2307846 |
MT-SDT over CG-SDT |
Apple |
| R2-2307934 |
Handling BWP restrictions in MT-SDT |
Ericsson, T-Mobile USA, Deutsche Telekom |
| R2-2307960 |
Remaining UP details for MT-SDT |
Lenovo |
| R2-2308081 |
MT SDT – UP Open Topics on ROHC and DVT |
Intel Corporation |
| R2-2308169 |
Beam failure recovery for Rel-18 SDT |
Sony, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2308171 |
User plane aspects for MT-SDT |
Sony |
| R2-2308242 |
User plane aspects of MT-SDT |
NEC |
| R2-2308348 |
User plane aspects of MT-SDT |
Huawei, HiSilicon |
| R2-2308406 |
Remining issues on user plane aspects of MT-SDT |
Qualcomm Incorporated |
| R2-2308656 |
Discussion on UP aspects of MT-SDT |
China Telecom |
| R2-2308927 |
Selection between CG-SDT and RACH based SDT |
Nokia, Nokia Shanghai Bell |
| 7.19.1 |
Organizational |
|
| R2-2307029 |
Reply LS on INACTIVE eDRX above 10.24sec and SDT (R3-233347; contact: Ericsson) |
RAN3 |
| R2-2307058 |
LS reply to RAN3 progress on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 (S2-2307730; contact: Huawei) |
SA2 |
| R2-2307256 |
Running CR for TS 38.300 for Rel-18 eRedCap |
OPPO |
| R2-2307301 |
Running MAC CR for eRedCap |
vivo (Rapporteur) |
| R2-2307447 |
Running 38.304 CR for enhanced support of reduced capability NR devices |
Huawei, HiSilicon |
| R2-2307657 |
UE Capabilities for Rel-18 eRedCap WI |
Intel Corporation |
| R2-2307658 |
UE Capabilities for Rel-18 eRedCap WI |
Intel Corporation |
| R2-2308238 |
[draft] LS on the guidance when capturing Rel-18 RedCap UEs in specifications |
Huawei, Ericsson |
| R2-2308804 |
Running RRC CR for eRedCap |
Ericsson |
| R2-2308805 |
Discussion on Msg4 PDSCH transmission to Rel-18 eRedCap UEs |
Ericsson |
| R2-2309063 |
Running CR for TS 38.300 for Rel-18 eRedCap |
OPPO |
| R2-2309064 |
Running 38.304 CR for enhanced support of reduced capability NR devices |
Huawei, HiSilicon |
| R2-2309067 |
Running MAC CR for eRedCap |
vivo (Rapporteur) |
| R2-2309068 |
Introduction of eRedCap |
Ericsson |
| 7.19.2 |
Enhanced eDRX in RRC_INACTIVE |
|
| R2-2307144 |
Remaining issues for Fallback behaviour for eRedcap UE |
NEC |
| R2-2307248 |
Discussion on enhanced eDRX in RRC_INACTIVE |
OPPO |
| R2-2307302 |
Remaining issues on enhanced eDRX for eRedCap |
vivo, Guangdong Genius |
| R2-2307420 |
Discussion on enhanced eDRX in RRC_INACTIVE |
CATT |
| R2-2307448 |
Discussion on enhanced eDRX in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2307595 |
Remaining issues of enhanced eDRX in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| R2-2307930 |
Discussion on enhanced eDRX in RRC_INACTIVE |
Samsung |
| R2-2308307 |
Discussion on eDRX in RRC_INACTIVE |
CMCC |
| R2-2308403 |
Remaining issues for enhanced eDRX in RRC_INACTIVE |
MediaTek Inc. |
| R2-2308407 |
Discussion on enhanced eDRX in RRC inactive |
Qualcomm Incorporated |
| R2-2308806 |
PTW configuration and fallback mechanism for RRC_INACTIVE eDRX |
Ericsson |
| 7.19.3 |
Further reduced UE complexity in FR1 |
|
| R2-2307170 |
Handling Msg4 and Msg2 with larger bandwidth |
Samsung Electronics Co., Ltd |
| R2-2307249 |
Discussion on Msg4 PDSCH with a larger bandwidth for eRedCap Ues |
OPPO |
| R2-2307257 |
Discussion on cellbarring for eRedCap UEs |
OPPO |
| R2-2307303 |
Discussion on access restriction for eRedCap |
vivo, Guangdong Genius |
| R2-2307304 |
Discussion on capability for eRedCap |
vivo, Guangdong Genius |
| R2-2307356 |
Discussion on early indication for eRedcap devices |
Xiaomi Communications |
| R2-2307361 |
[Draft] Drafted LS to RAN1 on early indication for eRedcap devices |
Xiaomi Communications |
| R2-2307362 |
Discussion on UE capabilities and other impacts for eRedcap devices |
Xiaomi Communications |
| R2-2307470 |
Further discussions on early indication and access restrictions for eRedCap |
NEC |
| R2-2307471 |
Discussion on issue of decoding Msg4 |
NEC |
| R2-2307485 |
Discussion on further UE complexity reduction |
CEPRI, CATT |
| R2-2307517 |
On access restrictions for enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| R2-2307597 |
Msg1 early indication for eRedCap UE |
ZTE Corporation, Sanechips |
| R2-2307599 |
Capability definition and report for eRedCap UE |
ZTE Corporation, Sanechips |
| R2-2307659 |
UE Capability Discussion for Rel-18 eRedCap WI |
Intel Corporation |
| R2-2307737 |
Discussion on RAN1 LS on Msg.4 PDSCH transmission |
vivo, Huawei, HiSilicon, Apple, MediaTek Inc., Qualcomm Inc., Ericsson, Intel Corporation, CMCC, Guangdong Genius |
| R2-2307931 |
Discussion on UE capability for eRedCap UEs |
Samsung |
| R2-2308237 |
Early identification and access restriction for eRedCap UEs |
Huawei, HiSilicon |
| R2-2308341 |
On enhanced RedCap capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2308404 |
Open aspects of initial access for eRedCap UEs |
MediaTek Inc. |
| R2-2308413 |
Discussion on further complexity reduction for eRedCap UE |
Qualcomm Incorporated |
| R2-2308551 |
Access restrictions for eRedCap UE |
Semtech Neuchatel SA |
| R2-2308673 |
Considerations on Further reduced UE complexity for eRedcap |
Sequans Communications |
| R2-2308746 |
Random access aspects |
Nokia, Nokia Shanghai Bell |
| R2-2308807 |
Access control for BB BW reduced UEs |
Ericsson |
| R2-2308808 |
Capability signalling for eRedCap UEs |
Ericsson |
| R2-2308814 |
Discussion on Cell barring for eRedCap |
NTT DOCOMO INC. |
| R2-2308825 |
Discussion on optional UE capability filter for eRedCap UE |
Qualcomm Incorporated, Ericsson, Intel, ZTE, Xiaomi |
| R2-2308877 |
Discussion on Msg1-based early indication for Rel-18 eRedCap UE |
LG Electronics Inc. |
| R2-2308878 |
Discussion on MsgA based early indication |
LG Electronics Inc. |
| R2-2308882 |
Access restrictions for eRedCap |
Nordic Semiconductor ASA |
| R2-2309061 |
Report from offline 751 |
vivo |
| R2-2309062 |
[Draft] Reply LS to RAN1 on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
vivo |
| R2-2309269 |
Reply LS to RAN1 on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
RAN2 |
| 7.20.1 |
Organizational |
|
| R2-2307018 |
Reply on LS 2TA for multi-DCI multi-TRP (R1-2306249; contact: Ericsson) |
RAN1 |
| R2-2308273 |
LS to RAN2 on CBSR for Rel-18 MIMO (R1-2308396; contact: Samsung) |
RAN1 |
| R2-2308342 |
Running CR for MIMO Evolution |
Ericsson |
| R2-2308358 |
Excel in R1-2306271 with rapporteur comments. |
Ericsson |
| 7.20.2 |
Two TAs for multi-DCI multi-TRP |
|
| R2-2307198 |
Discussion on multiple TAG |
OPPO |
| R2-2307224 |
Discussions on Two TAs for Multi-DCI Multi-TRP |
CATT |
| R2-2307316 |
Discussion on two TAs for multi-DCI multi-TRP |
Samsung |
| R2-2307317 |
Report of [Post122][852][MIMOevo] 2TAs for multi-DCI multi-TRP |
Samsung |
| R2-2307354 |
Discussion on modeling for PTAG |
SHARP Corporation |
| R2-2307355 |
Discussion on two TAs for multiple TRPs |
SHARP Corporation |
| R2-2307406 |
Considerations on multi-DCI multi-TRP operation with two Tas |
Fujitsu |
| R2-2307465 |
On 2TA operation |
Ericsson |
| R2-2307614 |
Two TAs for multi-DCI multi-TRP |
Huawei, HiSilicon |
| R2-2307673 |
TAT expiry and TAG modeling |
Xiaomi |
| R2-2307805 |
Discussion on TA maintenance in two TAs for multi-TRP |
LG Electronics Inc. |
| R2-2307847 |
Support of Two TAs for multi-DCI multi-TRP |
Apple |
| R2-2307899 |
Discussion on two TAs for multi-DCI multi-TRP |
FGI |
| R2-2307951 |
Discussion on TAG Management for Multi-TRP |
NEC Corporation |
| R2-2308028 |
Discussion on the impacts of Two TAs for multi-DCI multi-TRP operation |
Lenovo |
| R2-2308029 |
Discussion on the UE-initiated RACH procedure in multi-TRP operation |
Lenovo |
| R2-2308030 |
Consideration on RLF in multi-TRP operation |
Lenovo |
| R2-2308414 |
Discussion on multi-DCI multi-TRP with two TAs |
Qualcomm Incorporated |
| R2-2308530 |
UL time alignment in multi-DCI based multi-TRP with two TAs |
InterDigital |
| R2-2308816 |
Open issues on Two TAs for multi-DCI multi-TRP |
NTT DOCOMO INC. |
| R2-2308842 |
Consideration on the RRC parameter for 2TA |
ZTE Corporation,Sanechips |
| R2-2308843 |
Further consideration on the PCell Configured with two TA |
ZTE Corporation,Sanechips |
| R2-2308928 |
RA procedure while SpCell is configured with 2 TAGs |
Nokia, Nokia Shanghai Bell |
| R2-2308996 |
Reserved |
Reserved |
| 7.20.3 |
Unified TCI extension to mTRP operation |
|
| R2-2307199 |
Discussion on MAC CE design for mTRP |
OPPO |
| R2-2307225 |
Discussion on Unified TCI Framework Extension for sDCI based Multi-TRP |
CATT |
| R2-2307334 |
Discussion on multi-TRP with unified TCI states |
Nokia, Nokia Shanghai Bell |
| R2-2307466 |
On uTCI operation |
Ericsson |
| R2-2307615 |
Extension of unified TCI framework for mTRP |
Huawei, HiSilicon |
| R2-2307695 |
Single-DCI based unified TCI extension to multi-TRP operation |
Samsung |
| R2-2307806 |
Discussion on impact of multi-TRP on MAC CE |
LG Electronics Inc. |
| R2-2308415 |
Discussion on unified TCI framework extension for mTRP |
Qualcomm Incorporated |
| R2-2308817 |
Open issues on Unified TCI framework extension |
NTT DOCOMO INC. |
| R2-2308844 |
Further consideration on unified TCI State Extension for SDMT |
ZTE Corporation,Sanechips |
| R2-2308920 |
Design of mDCI MAC CE for Rel-18 MIMO |
Nokia, Nokia Shanghai Bell |
| R2-2308921 |
Design of sDCI MAC CE for Rel-18 MIMO |
Nokia, Nokia Shanghai Bell |
| R2-2308936 |
Discussion on MAC-CE design for M-TRP |
CEWiT |
| 7.20.4 |
Other |
|
| R2-2307464 |
On other parameters MIMOevo Rel18 |
Ericsson |
| R2-2307616 |
Intra-UE prioritization for STxMP |
Huawei, HiSilicon |
| R2-2307696 |
Discussion on Rel-18 higher-layers parameter list for MIMO |
Samsung |
| 7.21.1 |
Organizational |
|
| R2-2308065 |
Report of [Post122][802][R18CEenh-UP] UP open issues (ZTE) |
ZTE Corporation |
| R2-2308066 |
Running CR to 38.321 for Rel-18 coverage enhancements |
ZTE Corporation |
| R2-2308659 |
(draft CR to TS 38.300) On introduction of R18 CE-enh |
China Telecommunications |
| R2-2308663 |
Summary of [Post122][801][R18CEenh-CP] CP open issues (Huawei) |
Huawei, HiSilicon |
| R2-2308664 |
RRC Running CR for R18 NR coverage enhancements |
Huawei, HiSilicon |
| R2-2308665 |
Draft LS out on CFRA with MSG1 repetition |
Huawei, HiSilicon |
| R2-2309081 |
Report of [AT123][801][CE_enh] Discussion on issues needing RAN1 input (ZTE) |
Rapporteur (ZTE) |
| R2-2309255 |
LS on Power headroom information for assumed PUSCH (R1-2308376; contact: InterDigital) |
RAN1 |
| R2-2309256 |
LS on Details of power headroom information for assumed PUSCH (R1-2308477; contact: InterDigital) |
RAN1 |
| 7.21.2 |
Control plane issues |
|
| R2-2307115 |
Further Discussion on PRACH Repetition from CP |
vivo |
| R2-2307171 |
Remaining control plane issues of further NR Coverage Enhancements |
Samsung Electronics Co., Ltd |
| R2-2307421 |
Discussion on IE structure for MSG1 repetition |
CATT |
| R2-2307437 |
Further NR Coverage Enhancements CP Discussion |
Ericsson |
| R2-2307508 |
Discussion on control plane issues for coverage enhancement |
Xiaomi |
| R2-2307652 |
UL Coverage Enhancements Control Plane |
Qualcomm Incorporated |
| R2-2307799 |
Discussion on CP issues of Multiple PRACH Transmissions |
NEC Corporation |
| R2-2308068 |
Remaining CP issues for CE |
ZTE Corporation, Sanechips |
| R2-2308667 |
Discussion on RRC aspect with MSG1 repetition |
Huawei, HiSilicon |
| R2-2308670 |
Discussion on RRC aspect with MSG1 repetition |
Huawei, China Southern Power Grid, HiSilicon |
| R2-2308879 |
Signalling aspects for Msg1 repetition |
LG Electronics Inc. |
| 7.21.3 |
User plane issues |
|
| R2-2307116 |
Further Discussion on PRACH Repetition from UP |
vivo |
| R2-2307172 |
Remaining user plane issues of further NR Coverage Enhancements |
Samsung Electronics Co., Ltd |
| R2-2307422 |
Discussion on UP issues for MSG1 repetition |
CATT |
| R2-2307425 |
Further NR Coverage Enhancements UP Discussion |
Ericsson |
| R2-2307509 |
Discussion on user plane issues for coverage enhancement |
Xiaomi |
| R2-2307653 |
UL Coverage Enhancements User Plane |
Qualcomm Incorporated |
| R2-2307801 |
Discussion on UP issues of Multiple PRACH Transmissions |
NEC Corporation |
| R2-2308067 |
Remaining UP issues for CE |
ZTE Corporation, Sanechips |
| R2-2308392 |
Multiple PRACH transmissions – UP aspects |
InterDigital |
| R2-2308666 |
Discussion on MAC aspect with MSG1 repetition |
Huawei, HiSilicon |
| R2-2308880 |
RA procedure to support Msg1 repetition |
LG Electronics Inc. |
| R2-2308929 |
UP impacts of PRACH CE |
Nokia, Nokia Shanghai Bell |
| R2-2308930 |
PRACH CE fallback cases |
Nokia, Nokia Shanghai Bell |
| 7.22.1 |
Organizational |
|
| R2-2307305 |
Work Plan for Rel-18 SI on LP-WUS/WUR |
vivo (Rapporteur) |
| R2-2307306 |
Update of TR 38.869 for LP-WUS WUR |
vivo (Rapporteur) |
| R2-2309311 |
Update of TR 38.869 for LP-WUS WUR |
vivo (Rapporteur) |
| 7.22.2 |
Idle Inactive Mode |
|
| R2-2307082 |
Use of low-power receiver in RRC Idle/Inactive |
Qualcomm Incorporated |
| R2-2307261 |
Discussion on coverage impact for LP-WUR |
OPPO |
| R2-2307274 |
Discussion on LP-WUS in RRC IDLE and INACTIVE |
Continental Automotive |
| R2-2307307 |
Discussion on LP-WUS WUR in RRC_IDLE/INACTIVE |
vivo |
| R2-2307344 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2307423 |
Discussion on LP-WUS in RRC_IDLE&INACTIVE state |
CATT |
| R2-2307453 |
MR/LR UE behaviours for paging and mobility in RRC_IDLE/INACTIVE state |
Huawei, HiSilicon |
| R2-2307461 |
Discussion on the considerations for LPWUS in RRC_IDLE INACTIVE |
NEC Corporation |
| R2-2307516 |
LP-WUS in RRC IDLE and INACTIVE |
Nokia, Nokia Shanghai Bell |
| R2-2307591 |
RAN2 impacts of LP-WUS in idle or inactive mode |
ZTE Corporation, Sanechips |
| R2-2307848 |
RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state |
Apple |
| R2-2308168 |
Considerations on LP-WUR in RRC Idle/Inactive mode |
Sony |
| R2-2308460 |
LP-WUS in RRC Idle/ Inactive Mode |
Lenovo |
| R2-2308748 |
On LP-WUS in RRC_CONNECTED |
Nokia, Nokia Shanghai Bell |
| R2-2308809 |
LP-WUS/WUR for RRC Idle and Inactive |
Ericsson |
| R2-2308828 |
On impact to IDLE/INACTIVE procedures to support LP-WUR |
SAMSUNG R&D INSTITUTE INDIA |
| R2-2308977 |
RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state |
Apple |
| R2-2309267 |
Report of [Offline-026][LP-WUS] Idle/inactive aspects |
vivo |
| 7.22.3 |
Connected Mode |
|
| R2-2307083 |
Use of low-power receiver in RRC Connected |
Qualcomm Incorporated |
| R2-2307260 |
Discussion on LP-WUR’s operation |
OPPO |
| R2-2307308 |
Discussion on LP-WUS/WUR in RRC_Connected |
vivo |
| R2-2307345 |
Discussing on LP-WUS monitoring for RRC_Connected |
Xiaomi Communications |
| R2-2307424 |
Discussion on LP-WUS in RRC_CONNECTED state |
CATT |
| R2-2307449 |
High layer procedures for LP-WUS in RRC_CONNECTED state |
Huawei, HiSilicon |
| R2-2307462 |
Discussion on the considerations for LPWUS in RRC_CONNECTED |
NEC Corporation |
| R2-2307592 |
RAN2 impacts of LP-WUS in connected mode |
ZTE Corporation, Sanechips |
| R2-2307849 |
RAN2 impact of LP-WUS in RRC_CONNECTED state |
Apple |
| R2-2308461 |
LP-WUS in RRC Connected Mode |
Lenovo |
| R2-2308532 |
Discussion on LP-WUS in RRC_CONNECTED |
Continental Automotive |
| R2-2308810 |
LP-WUS/WUR for RRC Connected |
Ericsson |
| 7.23 |
Timing Resiliency and URLLC Enh |
|
| R2-2307654 |
Clock Quality Report Delivery |
Qualcomm Incorporated |
| 7.23.1 |
Organizational |
|
| R2-2307051 |
Response to Reply LS on Proposed method for Time Synchronization status reporting to UE(s) (S1-231285; contact: Nokia) |
SA1 |
| R2-2307791 |
Stage 2 running CR on timing resiliency and URLLC |
Nokia, Nokia Shanghai Bell |
| R2-2308531 |
Introduction of URLLC and Timing Resiliency |
Ericsson |
| 7.23.2 |
General |
|
| R2-2307114 |
Discussion on Timing Synchronization Status Monitoring |
vivo |
| R2-2307352 |
RAN2 Impact of 5GS network timing synchronization status and reporting |
CATT |
| R2-2307502 |
Remaining issues for NR Timing Resiliency |
Ericsson |
| R2-2307560 |
Discussion on remaining issues for TRS |
Huawei, Hisilicon, China Southern Power Grid |
| R2-2307600 |
Remaining issues of time synchronization status and reporting |
ZTE Corporation, Sanechips |
| R2-2307759 |
Open Issues on Timing Synchronization |
Samsung |
| R2-2307782 |
5GS network timing synchronization status and reporting |
Xiaomi |
| R2-2307792 |
5GS network timing synchronization status and reporting |
Nokia, Nokia Shanghai Bell |
| R2-2307838 |
UE Access for 5GS Network Timing Synchronization |
Apple |
| R2-2308308 |
Discussion on the network timing synchronization status monitoring |
CMCC |
| R2-2308658 |
Discussion on Time Synchronization Status and Reporting |
China Telecom |
| R2-2309264 |
LS on Event ID broadcast in SIB9 |
RAN2 |
| 7.24.1 |
TEI proposals by Other Groups |
|
| R2-2307009 |
LS on 1-symbol PRS (R1-2306212; contact: ZTE) |
RAN1 |
| R2-2308140 |
Introduction of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2308141 |
Introduction of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2308142 |
Introduction of UE capability of 1-symbol PRS in 37.355[1symbol_PRS] |
ZTE Corporation |
| R2-2308143 |
Introduction of UE capability of 1-symbol PRS in 38.331[1symbol_PRS] |
ZTE Corporation |
| R2-2308144 |
Introduction of UE capability of 1-symbol PRS in 38.306[1symbol_PRS] |
ZTE Corporation |
| R2-2308269 |
LS on Mitigation of Downgrade attacks (S3-234173; contact: Vodafone) |
SA3 |
| R2-2308938 |
Network support and clarification of redirection to 3G |
Vodafone, Orange, Deutsche Telekom |
| R2-2308975 |
Network support and clarification of redirection to 3G |
Vodafone, Orange, Deutsche Telekom |
| 7.24.2 |
TEI proposals by RAN2 |
|
| R2-2307176 |
Paging Cause forwarding |
Samsung Electronics Co., Ltd |
| R2-2307183 |
Simple solution on Inter-frequency measurements |
Lenovo |
| R2-2307237 |
Discussion on emergency cause value for SL Relay |
OPPO |
| R2-2307242 |
Discussion on inter-frequency measurement |
OPPO |
| R2-2307335 |
Signalling overhead reduction of DC location reporting signalling [DCLoc-Overhead] |
Nokia, Nokia Shanghai Bell |
| R2-2307342 |
Multiple QoS for positioning |
MediaTek Inc. |
| R2-2307537 |
Extended periodicity for CG-SDT |
ZTE Corporation, Sanechips |
| R2-2307694 |
Discussion on MUSIM paging cause forwarding |
vivo |
| R2-2307757 |
Support for SSR Satellite PCV Residuals |
Swift Navigation |
| R2-2307800 |
Further Discussion on Using RedCap-specific Broadcast CFR |
vivo |
| R2-2307802 |
Discussion on longer periodicity for CG-SDT |
NEC Corporation |
| R2-2307851 |
RRC segment transmission continuity |
Apple |
| R2-2307957 |
Discussion on adding longer CG-SDT periodicities |
Ericsson |
| R2-2307965 |
Enhancement to maintain high data rate during DAPS handover |
Huawei, HiSilicon, China Telecom, China Unicom, CMCC |
| R2-2307974 |
PTM retransmission reception by UEs without HARQ feedback |
Nokia, Nokia Shanghai Bell, AT&T, Qualcomm |
| R2-2308193 |
NavIC L5 A-GNSS support updates to RRC protocol specification |
Reliance Jio |
| R2-2308332 |
Discussion on the issue of unpredictable measurement sequence for inter-frequency measurement reporting and candidate solutions |
CMCC |
| R2-2308346 |
Corrections on RedCap UE MBS Broadcast reception |
ZTE, Sanechips |
| R2-2308442 |
Priority order of inter-frequency measurements |
Ericsson |
| R2-2308485 |
Relay based Positioning posSIB forwarding |
Ericsson, Deutsche Telekom, AT&T |
| R2-2308486 |
Information on posSIBs relaying to remote UE [PosL2RemoteUE] |
Ericsson, Deutsche Telekom, AT&T |
| R2-2308487 |
Information on posSIBs relaying to remote UE |
Ericsson, Deutsche Telekom, AT&T |
| R2-2308489 |
Adding support for Bluetooth AoA/AoD |
Ericsson, AT&T, Polaris Wireless, u-blox |
| R2-2308641 |
Discussion on UE behaviours of delay measurements upon MO updates |
Huawei, HiSilicon |
| R2-2308695 |
Discussion on positioning support for L2 U2N remote UE |
Samsung |
| R2-2308771 |
Discussion on the issue of unpredictable measurement report sequence |
vivo |
| R2-2308773 |
Discussion on unpredictable inter-frequency measurement reporting |
MediaTek Inc. |
| R2-2308830 |
Introduction of ‘multiple QoS’ class in positioning |
Samsung Electronics Romania |
| R2-2308845 |
Ranges and Values which might be “hard to explain” |
Vodafone Italia SpA, Orange, Qualcomm |
| R2-2308846 |
Protection against improper reselection to GERAN |
Vodafone, Orange, Qualcomm |
| R2-2308848 |
Network support and clarification of redirection to 3G |
Vodafone, Orange |
| R2-2308885 |
Open Issue on RedCap CFR for MBS broadcast |
CATT |
| R2-2308932 |
Considerations on voice and video support for Relays |
Philips International B.V., FirstNet, InterDigital, KPN, TNO, |
| R2-2308945 |
Enhancement to maintain high data rate during DAPS handover |
Huawei, HiSilicon, China Telecom, China Unicom |
| R2-2308955 |
Adding support for Bluetooth AoA/AoD |
Ericsson, AT&T, Polaris Wireless, u-blox, T-Mobile |
| R2-2308976 |
Protection against improper reselection to GERAN |
Vodafone, Orange, Qualcomm |
| R2-2308978 |
Correction on GNSS-ID for NavIC A-GNSS |
Reliance Jio, CEWiT |
| R2-2309107 |
[AT123][424][POS] Network control of posSIBs for remote UEs (Ericsson) |
Ericsson |
| R2-2309108 |
[AT123][426][POS] BT AoA/AoD (Ericsson) |
Ericsson (Moderator) |
| R2-2309112 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift, Ericsson |
| R2-2309113 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift, Ericsson |
| R2-2309114 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift, Ericsson |
| R2-2309115 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift, Ericsson |
| R2-2309116 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift, Ericsson |
| R2-2309170 |
[AT123][425][POS] Proposals on positioning for remote UE (Samsung) |
Samsung (Moderator) |
| R2-2309230 |
[AT123][408][POS] Rel-18 positioning RRC CR (Ericsson) |
Ericsson |
| R2-2309320 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift Navigation, Ericsson |
| R2-2309321 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift Navigation, Ericsson |
| R2-2309322 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift Navigation, Ericsson |
| R2-2309323 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift Navigation, Ericsson |
| R2-2309324 |
SSR Satellite PCV Residuals [Rel18PCV] |
Swift Navigation, Ericsson |
| 7.25.1 |
RAN4 led items |
|
| R2-2307019 |
Reply LS on RS supported for group-based reporting (R1-2306257; contact: Ericsson) |
RAN1 |
| R2-2307036 |
Response LS on extending the maximum range for NS values (R4-2306560; contact: Apple) |
RAN4 |
| R2-2307037 |
LS on UE features for NR ATG (R4-2309797; contact: CMCC) |
RAN4 |
| R2-2307038 |
Reply LS on applicability of SIB19 for NR ATG (R4-2310058; contact: Qualcomm) |
RAN4 |
| R2-2307039 |
LS on FR2 SCell activation enhancements (R4-2310083; contact: Apple) |
RAN4 |
| R2-2307040 |
LS on signaling for NR ATG (R4-2310152; contact: Ericsson) |
RAN4 |
| R2-2307041 |
LS on inter-RAT measurements without gaps (R4- 2310158; contact: Intel) |
RAN4 |
| R2-2307045 |
LS on lower MSD capability (R4-2310276; contact: Huawei) |
RAN4 |
| R2-2307047 |
Response LS on extending the maximum range for NS values (R4-2310474; contact: Apple) |
RAN4 |
| R2-2307095 |
Discussion on MSD Capability |
OPPO |
| R2-2307275 |
Discussion on inter-RAT LTE measurements without gap |
CATT |
| R2-2307276 |
Discussion on open issues of ATG |
CATT |
| R2-2307277 |
Discussion on the support of lower MSD |
CATT |
| R2-2307278 |
Discussion on FR2 unknown SCell activation enhancement |
CATT |
| R2-2307309 |
RRM measurement for option B-1-1 and option C for BWP Wor |
vivo, Guangdong Genius |
| R2-2307310 |
Correction on 38.300 for BWP Wor |
vivo, Vodafone |
| R2-2307311 |
Correction on 38.331for BWP Wor |
vivo |
| R2-2307312 |
Correction on 38.306 for BWP Wor |
vivo |
| R2-2307336 |
Lower MSD capability |
Nokia, Nokia Shanghai Bell |
| R2-2307457 |
Discussion on SI for ATG |
Ericsson |
| R2-2307510 |
Discussion on the support of ATG |
Xiaomi |
| R2-2307543 |
Consideration on Lower MSD Capability Signaling |
ZTE Corporation, Sanechips |
| R2-2307575 |
On RAN2 Impacts of Air-To-Ground (ATG) in Rel-18 |
Nokia, Nokia Shanghai Bell |
| R2-2307630 |
Discussion on the support of Air to ground access |
Qualcomm Incorporated |
| R2-2307676 |
Discussion on the lower MSD capability |
Xiaomi |
| R2-2307769 |
Cross RRH TCI state switch |
Nokia, Nokia Shanghai Bell |
| R2-2307770 |
Scell activation and L3 reporting |
Nokia, Nokia Shanghai Bell |
| R2-2307850 |
FR2 SCell Enhancement |
Apple |
| R2-2307877 |
Addition of extended number range for NS value |
Apple, Ericsson, Lenovo |
| R2-2307878 |
Addition of extended number range for NS value |
Apple, Ericsson, Lenovo |
| R2-2307879 |
Handling Rel-17 DC location signaling enhancement |
Apple |
| R2-2308047 |
Discussion on effective measurement window |
Huawei, HiSilicon |
| R2-2308070 |
Discussion on ATG |
ZTE Corporation, Sanechips |
| R2-2308071 |
Discussion on inter-RAT LTE measurements without gap |
ZTE Corporation, Sanechips |
| R2-2308072 |
Discussion on FR2 unknown SCell activation |
ZTE Corporation, Sanechips |
| R2-2308202 |
Measurement reporting for FR2 unknown SCell activation enhancement |
LG Electronics Inc. |
| R2-2308208 |
RAN2 signalling design for FR2 unknown SCell activation enhancement |
Huawei, HiSilicon |
| R2-2308236 |
On inter-RAT LTE measurements without gap |
Nokia, Nokia Shanghai Bell |
| R2-2308443 |
Introduction of FR2 SCell enhancements |
Ericsson |
| R2-2308453 |
Support for BWP operation without restriction (Option C) |
ZTE Corporation, Sanechips |
| R2-2308454 |
Support for BWP operation without restriction |
ZTE Corporation, Sanechips |
| R2-2308455 |
Support for BWP operation without restriction |
ZTE Corporation, Sanechips |
| R2-2308495 |
Support of lower MSD capability |
Ericsson |
| R2-2308637 |
Discussion on MAC-CE based indication for cross-RRH TCI state switch |
Huawei, HiSilicon |
| R2-2308638 |
Draft CR to 38.321 for HST-FR2 |
Huawei, HiSilicon |
| R2-2308639 |
Draft CR to 38.331 for HST-FR2 |
Huawei, HiSilicon |
| R2-2308640 |
Draft CR to 38.306 for HST-FR2 |
Huawei, HiSilicon |
| R2-2308766 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2308767 |
Introduction of measurements without gap with interruption |
MediaTek Inc., Huawei, HiSilicon |
| R2-2308768 |
Running CR for further measurement gap enhancements |
MediaTek Inc., Huawei, HiSilicon |
| R2-2308769 |
Running CR for further measurement gap enhancements capabilities |
MediaTek Inc., Huawei, HiSilicon |
| R2-2308770 |
Running CR for further measurement gap enhancements capabilities |
MediaTek Inc., Huawei, HiSilicon |
| R2-2308774 |
Discussion on inter-RAT measurements without gaps |
vivo |
| R2-2308775 |
Discussion on lower MSD signalling |
vivo |
| R2-2308776 |
Discussion on DC location signaling enhancement |
vivo |
| R2-2308835 |
Discussion on FR2 unknown SCell activation enhancement |
vivo |
| R2-2308847 |
Discussion on the reply LS on applicability of SIB19 for NR ATG |
CMCC |
| R2-2308863 |
Discussion on lower MSD capability |
Huawei, HiSilicon |
| R2-2308864 |
Introduction of lower MSD capability |
Huawei, HiSilicon |
| R2-2308865 |
Introduction of lower MSD capability |
Huawei, HiSilicon |
| R2-2308896 |
On air-to-ground system information and other adaptations |
Samsung Electronics Czech |
| R2-2308948 |
Discussion on MSD Capability |
OPPO |
| R2-2309168 |
Addition of extended number range for NS value |
Apple Inc, Ericsson, Lenovo |
| R2-2309169 |
Addition of extended number range for NS value |
Apple Inc, Ericsson, Lenovo |
| R2-2309253 |
Report of [At123][025] FR2 SCell Enhancement |
Apple |
| R2-2309254 |
Introduction of FR2 SCell enhancements |
Apple |
| 7.25.2 |
RAN1 led items |
|
| R2-2307044 |
Reply LS on report of switching periods in Rel-18 uplink Tx switching (R4-2310271; contact: NTT DOCOMO) |
RAN4 |
| R2-2307048 |
LS on multi-carrier enhancement (R4-2310495; contact: vivo) |
RAN4 |
| R2-2307153 |
Discussion on RRC signalling for MC enhancements |
Xiaomi |
| R2-2307154 |
Introduction of Multi-cell Scheduling |
Xiaomi |
| R2-2308209 |
Further updates to the RAN2 CRs for Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon |
| R2-2308734 |
TP to BLCR of 38 331 for RRC configuration |
CATT |
| R2-2308735 |
Discussion on UE capability reporting (with TP to TS38.331 BLCR) |
CATT |
| R2-2308736 |
Discussion on UE capability reporting (with TP to TS38.306 BLCR) |
CATT |
| R2-2308802 |
Draft CR for introduction of RRC configuration for multi-cell PDSCH/PUSCH scheduling |
NTT DOCOMO INC., Huawei, HiSilicon |
| R2-2308815 |
On introduction of multi-cell scheduling |
NTT DOCOMO INC. |
| R2-2309238 |
TP to BLCR of 38 331 for RRC configuration |
CATT |
| 7.25.3 |
Other |
|
| R2-2307027 |
Response LS on Partially Allowed/Rejected S-NSSAI (R3-233433; contact: Nokia) |
RAN3 |
| R2-2307619 |
Discussion on RAN impacts of further NPN enhancement |
Lenovo |
| R2-2307948 |
Discussion on remaining issues of eNPN in R18 |
China Telecom |
| R2-2307949 |
Draft CR to TS 38.306 on introduction of R18 eNPN |
China Telecom |
| R2-2308048 |
Discussion on RAN impact for NPN enhancement in Rel-18 |
Huawei, HiSilicon |
| R2-2308270 |
LS on the user consent for trace reporting (S3-234267; contact: Ericsson) |
SA3 |
| R2-2308400 |
On Positioning Reference Unit support in LPP |
Qualcomm Incorporated |
| R2-2308488 |
On the Positioning Reference Units aspects |
Ericsson, vivo |
| R2-2308635 |
Discussion on NAS-AS interaction of NS-AoS |
Huawei, HiSilicon |
| R2-2308636 |
CR on NAS-AS interaction of NS-AoS for TS 38.304 |
Huawei, HiSilicon |
| R2-2308675 |
Discussion on UE capability for R18 eNPN |
vivo |
| R2-2308765 |
Remaining issues on Further Enhancement NPN |
CATT |
| R2-2308917 |
NPN Rel-18 capabilities |
Ericsson |
| R2-2309120 |
[AT123][419][POS] Location information type for PRUs (Ericsson) |
Ericsson |
| 7.25.4 |
Self-Evaluation NTN |
|
| R2-2307322 |
Discussion on IMT-2020 Satellite self-evaluation for Latency and Mobility |
THALES |
| R2-2307496 |
Self-Evaluation for NR NTN |
Huawei, HiSilicon |
| R2-2307586 |
On CP and UP Latency for IMT-2020 NTN Self Evaluation |
Nokia, Nokia Shanghai Bell |
| R2-2307624 |
RAN2 aspects on evaluation methodology for IMT-2020 Satellite |
Qualcomm Incorporated |
| R2-2308508 |
Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology |
ZTE Corporation, Sanechips |
| R2-2308903 |
Satellite IMT-2020 self-evaluation: CP latency |
Ericsson |
| R2-2308905 |
Satellite IMT-2020 self-evaluation: UP latency |
Ericsson |
| R2-2308982 |
CP/UP latency assumptions |
Ericsson |
| 8.1 |
Session on NR NTN and IoT NTN |
|
| R2-2308961 |
Report from Break-Out Session on NR NTN and IoT NTN |
Vice Chairman (ZTE) |
| 8.2 |
Session on LTE legacy, XR, QoE and Multi-SIM |
|
| R2-2308962 |
Report from session on LTE legacy, XR, QoE and Multi-SIM |
Vice Chairman (Nokia) |
| 8.3 |
Session on UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
|
| R2-2308963 |
Report from UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
Session chair (InterDigital) |
| 8.4 |
Session on positioning and sidelink relay |
|
| R2-2308964 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 8.5 |
Session on LTE V2X and NR SL |
|
| R2-2308965 |
Report from session on LTE V2X and NR SL |
Session chair (Samsung) |
| 8.6 |
Session on SON/MDT |
|
| R2-2308966 |
Report from SON/MDT session |
Session chair (CMCC) |
| 8.7 |
Session on MBS |
|
| R2-2308967 |
Report from MBS breakout session |
Session chair (Huawei) |
| 8.8 |
Session on IDC |
|
| R2-2308968 |
Report from IDC breakout session |
Session chair (Intel) |
| 8.9 |
Session on NC Repeater |
|
| R2-2308969 |
Report from NC Repeater breakout session |
Session chair (Apple) |
| 8.10 |
Session on eRedCap |
|
| R2-2308970 |
Report from eRedCap breakout session |
Session chair (Ericsson) |
| 8.11 |
Session on Further NR coverage enhancements |
|
| R2-2308971 |
Report from Further NR coverage enhancements session |
Session chair (ZTE) |
| 8.12 |
Session on NR MIMO evolution |
|
| R2-2308972 |
Report from NR MIMO evolution session |
Session chair (CATT) |